| # |
Jul 21st 2009, 18:40 |
ProLoser|Work |
i don't like the idea of a working peice of code being all the way in another section from discussion articles that may show what lead up to its creation |
| # |
Jul 21st 2009, 18:40 |
ProLoser|Work |
i just think when i'm looking at code, i can find nearby the relevent documentation on people who use it, examples of how it was used, or alternatives, snippets that led to it |
| # |
Jul 21st 2009, 18:39 |
ProLoser|Work |
but that's not the point i'm emphasizing |
| # |
Jul 21st 2009, 18:39 |
ProLoser|Work |
it's all very github/chaw like |
| # |
Jul 21st 2009, 18:39 |
ProLoser|Work |
it has a team of people working on it, it has an established code section |
| # |
Jul 21st 2009, 18:39 |
ProLoser|Work |
this is an example module |
| # |
Jul 21st 2009, 18:39 |
ProLoser|Work |
i am aiming to become as successful as drupal in this endeavor: http://drupal.org/project/modules?filters=tid:75andsolrsort=sort_title%20asc |
| # |
Jul 21st 2009, 18:38 |
ProLoser|Work |
well |
| # |
Jul 21st 2009, 18:38 |
pointlessjon |
I'm not sure I'm doing this justice -- I'll just have to show you something visually -- and perhaps you could do the same? |
| # |
Jul 21st 2009, 18:37 |
ProLoser|Work |
one-off documents? |
| # |
Jul 21st 2009, 18:37 |
ProLoser|Work |
i was requestion that they establish a form of linking |
| # |
Jul 21st 2009, 18:37 |
pointlessjon |
Articles, such as tools, tutorial, snippets, are more like one-off documents |
| # |
Jul 21st 2009, 18:37 |
ProLoser|Work |
i think that's clear they do not plan to mirror that on bakery 2 |
| # |
Jul 21st 2009, 18:36 |
pointlessjon |
including all those things |
| # |
Jul 21st 2009, 18:36 |
pointlessjon |
as i understand it, code items are becoming almost like github repos or chaw projects |
| # |
Jul 21st 2009, 18:36 |
ProLoser|Work |
so that usecases and documentation can be built up around it |
| # |
Jul 21st 2009, 18:36 |
ProLoser|Work |
i'm saying keep code near it's related articles |
| # |
Jul 21st 2009, 18:35 |
ProLoser|Work |
i'm not saying cause ambiguouty by calling everything code |
| # |
Jul 21st 2009, 18:35 |
ProLoser|Work |
this is an example of how it's used |
| # |
Jul 21st 2009, 18:35 |
ProLoser|Work |
this is the code to use |
| # |
Jul 21st 2009, 18:35 |
pointlessjon |
ah yes, code will have that |
| # |
Jul 21st 2009, 18:35 |
ProLoser|Work |
'this is the tutorial |
| # |
Jul 21st 2009, 18:35 |
ProLoser|Work |
i know, so clearly break it apart into what is what |
| # |
Jul 21st 2009, 18:35 |
pointlessjon |
if it's in the article section, that article may contain 'code' in it for purposes of demonstration - but it is not meant to be dropped into an app |
| # |
Jul 21st 2009, 18:34 |
ProLoser|Work |
it would be nice to see the code, plus a tutorial on how to use it, plus snippets pertaining to the same vendor, plus an example of how it could be used, all be found in the same location |
| # |
Jul 21st 2009, 18:34 |
pointlessjon |
A content, item, node, etc. that is put in the code section contains portable, usable, stable code |
| # |
Jul 21st 2009, 18:34 |
ProLoser|Work |
and that's pretty much what we have now in bakery 1 |
| # |
Jul 21st 2009, 18:33 |
ProLoser|Work |
i thought you conceded that it creates a blob for the other areas that aren't code |
| # |
Jul 21st 2009, 18:33 |
pointlessjon |
exactly like the ticket (?) |
| # |
Jul 21st 2009, 18:33 |
ProLoser|Work |
so how would you organize them? |
| # |
Jul 21st 2009, 18:33 |
ProLoser|Work |
? |
| # |
Jul 21st 2009, 18:33 |
pointlessjon |
err, just aren't |
| # |
Jul 21st 2009, 18:33 |
pointlessjon |
those are articles with examples of code in them |
| # |
Jul 21st 2009, 18:32 |
pointlessjon |
no, those just are categorized as code |
| # |
Jul 21st 2009, 18:32 |
ProLoser|Work |
ur leaving those out |
| # |
Jul 21st 2009, 18:32 |
ProLoser|Work |
what about articles, tuts, snippets? |
| # |
Jul 21st 2009, 18:32 |
ProLoser|Work |
so that's /code/ |
| # |
Jul 21st 2009, 18:32 |
ProLoser|Work |
okay |
| # |
Jul 21st 2009, 18:32 |
pointlessjon |
imho |
| # |
Jul 21st 2009, 18:32 |
ProLoser|Work |
component/behavior/helper makes sense for categorization, i just wanted to abstract it so that other items that ARENT code could be categorized in the same way |
| # |
Jul 21st 2009, 18:32 |
pointlessjon |
right. any code in the code section should be ready to be dropped into an app with little to no code modification, only implementation into your app |