-
Posts
374 -
Joined
-
Last visited
-
Days Won
8
Everything posted by clsource
-
Good read, thanks. I will change the templates and pages analogies in the atomic design because it could mess with ProcessWire terminology. So you could separate a system in three main layers: # Presentation Layer (Frontend) atoms => basic html, css, js tags molecules => combination of different atoms (search bar, navigation menu, etc) organism => combination of different molecules (header : logo molecule + menu molecule + search bar molecule) artifact => combination of different organisms (wireframes, mockups) unit => an artifact in its final form (mockups are implemented with final looks and data) (ex: an static html page with static data) # Logic Layer (Backend) phenotype => Define what and how information is stored and represented in the storage system (username:Text, email:Text, password:Text, profileImage:Blob, etc). genotype => Define the group of phenotypes that a cell should fill. (an User needs the following information: username and password) cell => It's a representation of a genotype (User) with all the phenotype information filled (username:clsource, password:1234) # Execution Layer (Runtime, Final Product) entity = a unit that interacts with cells. (ex: a page with dynamic data)
-
Hello, I was reading about biology and maybe ProcessWire Template, Pages and Fields could be explained using Genotypes, Phenotypes and Cells. https://en.wikipedia.org/wiki/Genotype https://en.wikipedia.org/wiki/Phenotype https://en.wikipedia.org/wiki/Cell_(biology) Wikipedia Quotes So by using a wide interpretation of those definitions we could associate Templates = Genotypes (Defines the basic structure) Fields = Phenotypes (Defines what information will be stored an available for querying) Pages = Cells (It's the representation of the Template (Genotype) and Fields (Phenotypes) with the information filled. The basic structural unit for the ProcessWire application.) What do you think?
-
Hello, As you can see the blog rss is not updating since April http://processwire.com/blog/rss/ Weird :S
-
Hello, it´s an iOS thing. https://wouterdeschuyter.be/blog/how-to-disable-viewport-scaling-in-ios-10-you-dont-941140811 You should configure your safari
- 2 replies
-
- 2
-
- front end editing
- apple
-
(and 1 more)
Tagged with:
-
ProcessWire's Image Field Markdown Code Additional Fields
clsource replied to clsource's topic in Modules/Plugins
Yep, It's super cool that module. You can use both- 2 replies
-
- 1
-
- image field
- markdown
-
(and 1 more)
Tagged with:
-
Haha, I made a module also xd. Well the implementation is different but the use case is similar and complementary Good Module Robin
-
ProcessWire's Image Field Markdown Code Additional Fields
clsource posted a topic in Modules/Plugins
Hello, A friend posted a question about how obtain the markdown code for a image when you are using the markdown editor. Here I created a module just for that. You can download it here. https://github.com/NinjasCL/InputfieldImageMarkdownCodeAdditionalFields cheers.- 2 replies
-
- 6
-
- image field
- markdown
-
(and 1 more)
Tagged with:
-
Hello, you have to click the image and copy the path then use the markdown for images. Here´s a request that I made some time ago. https://github.com/ryancramerdesign/ProcessWire/issues/1954
-
this is wonderful news, thank you. here are the official docs https://github.com/github/linguist#overrides
-
Hello, I know there are a lot of installing processwire tutorials out there, but here I put mine (with images and other little things) https://dev.to/clsource/installing-processwire hope you like it
-
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 http://jasonette.com technology. You can compile your own app if you want. For A Quick Look 1.- Download the Jason App (iOS) https://itunes.apple.com/us/app/jason./id1095557868?mt=8 (Android) https://play.google.com/store/apps/details?id=com.jasonette.jason 2.- Use the Following Url https://raw.githubusercontent.com/NinjasCL/pw-app/master/app.json Source Here https://github.com/NinjasCL/pw-app
-
Markup Regions...Idea for another Placement Attribute
clsource replied to rastographics's topic in API & Templates
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. -
Interesting, Its similar to https://www.nativescript.org
- 1 reply
-
- 1
-
As a personal experience I would not recommend taking equity only projects. They are too risky.
-
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']);
- 2 replies
-
- 2
-
- translation
- pw
-
(and 1 more)
Tagged with:
-
Hello, In this tutorial I show how to use the wirePopulateStringTags function in order to improve translatable strings. https://medium.com/@clsource/better-translatable-strings-in-processwire-621e9e6b18ee#.tv2u23j4i 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}
- 2 replies
-
- 9
-
- translation
- pw
-
(and 1 more)
Tagged with:
-
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.
-
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?
-
May be you can use two approaches. One is creating an API inside PW using special templates and responses. maybe using my Rest Helper https://github.com/NinjasCL/pw-rest heres an example https://github.com/NinjasCL/voxgram The other one is creating an API outside PW using an specialized rest framework and calling PW using composer. http://flightphp.com http://phpsx.org http://phpflow.com/php/restful-api-frameworks-for-php/
-
Maybe using a forum software with a nice REST API will help you accesing data and performing actions like creating users and log them in. some good modern software are http://flarum.org/docs/api/ http://www.discourse.org