• Content count

  • Joined

  • Last visited

  • Days Won


clsource last won the day on January 21

clsource had the most liked content!

Community Reputation

442 Excellent

About clsource

  • Rank
    Sr. Member
  • Birthday 10/18/1989

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location

Recent Profile Visitors

5,320 profile views
  1. Its just a spotify playlist . If you want to share it you can use the code
  2. I created a simple playlist
  3. this is wonderful news, thank you. here are the official docs
  4. Thank you. Added an special thanks section
  5. Hello, I know there are a lot of installing processwire tutorials out there, but here I put mine (with images and other little things) hope you like it
  6. I recently bought an Android and iOS developer licenses so I can create a stand alone version of the app. That maybe will solve most problems
  7. Hello I made a simple app for reading the main RSS for ProcessWire news. Now you can access ProcessWire Blog, ProcessWire weekly and the Latest Forum Posts in a Single App in your iOS or Android smartphone. Open Source of Course. Made using the technology. You can compile your own app if you want. For A Quick Look 1.- Download the Jason App (iOS) (Android) 2.- Use the Following Url Source Here
  8. I think another way to do it is using <head pw-append="head"> ... </head> I don´t know for sure, . may be it works too.
  9. Interesting, Its similar to
  10. As a personal experience I would not recommend taking equity only projects. They are too risky.
  11. This is a shorthand function. So its easier to populate tags. /** * Perform a language translation replacing string tags. * * Used as an alternative to sprintf in language string that requires variables. * uses wirePopulateStringTags function for replacing tags. * * The $vars may also be an object, in which case values will be pulled as properties of the object. * * By default, tags are specified in the format: {first_name} where first_name is the name of the * variable to pull from $vars, '{' is the opening tag character, and '}' is the closing tag char. * * The tag parser can also handle subfields and OR tags, if $vars is an object that supports that. * For instance {products.title} is a subfield, and {first_name|title|name} is an OR tag. * * @param string $text Text for translation. * @param WireData|object|array $vars Object or associative array to pull replacement values from. * @param string $context Name of context * @param string $textdomain Textdomain for the text, may be class name, filename, or something made up by you. If omitted, a debug backtrace will attempt to determine automatically. * @param array $options Array of optional changes to default behavior, including: * - tagOpen: The required opening tag character(s), default is '{' * - tagClose: The optional closing tag character(s), default is '}' * - recursive: If replacement value contains tags, populate those too? Default=false. * - removeNullTags: If a tag resolves to a NULL, remove it? If false, tag will remain. Default=true. * - entityEncode: Entity encode the values pulled from $vars? Default=false. * - entityDecode: Entity decode the values pulled from $vars? Default=false. * @return string Translated text or original text if translation not available. * */ function _st($text, $vars, $context = null, $textdomain = null, array $options = array()) { return wirePopulateStringTags(__($text, $textdomain, $context), $vars, $options); } echo _st('There are {count} {items} in the {place}', ['count' => 5, 'items' => 'oranges', 'place' => 'tree']);
  12. Hello, In this tutorial I show how to use the wirePopulateStringTags function in order to improve translatable strings. Basically it will improve how the strings are shown in the translation administration. echo wirePopulateStringTags( __('There are {count} {items} in the {place}'), ['items' => 'apples', 'count' => 32, 'place' => 'basket'] ); Will render There are 32 apples in the basket And the Translator will see There are {count} {items} in the {place}
  13. Congrats for the Great Work. I wonder how you will distribute the site. Please write an article about your experience so we can learn how to do the same :). How you will manage updates? (specially database related ones) cheers.
  14. Technically my rest helper is just some functions that I used when creating simple Rest backend with ProcessWire. So is nothing too fancy, just what I needed. See the voxgram repo that used the Rest Helper . The magic with PW is that you can integrate it with more sophisticated tools like Symphony components using composer if you want to. May be I should write a simple tutorial using Rest and PW?
  15. May be you can use two approaches. One is creating an API inside PW using special templates and responses. maybe using my Rest Helper heres an example The other one is creating an API outside PW using an specialized rest framework and calling PW using composer.