Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Elgg development
Home
+ new post
About this group
Join this group
Teaching by git branch diffs
Options
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
   3 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Steve Clay  
View profile  
 More options Aug 16 2012, 9:57 pm
From: Steve Clay <st...@elgg.org>
Date: Thu, 16 Aug 2012 21:57:36 -0400
Local: Thurs, Aug 16 2012 9:57 pm
Subject: Teaching by git branch diffs
Print | Individual message | Show original | Report this message | Find messages by this author
I created a repo designed to simply show how Elgg features can be implemented. The master
branch is an empty plugin, and each branch will implement one feature to demonstrate usage
of views/menu items/etc.
https://github.com/Elgg/ShowMe

I created a couple branches to start with:
https://github.com/Elgg/ShowMe/compare/add-css
https://github.com/Elgg/ShowMe/compare/override-view

The good:
* trivially easy to create a branch to teach something
* lives in GitHub, where we want programmers contributing away
* easy for non-core GH users to submit branches
* Even non-accepted branches could be seen on the user's fork

The bad:
* currently no obvious place to offer feedback. We could direct feedback to this list/the
community, or issues on the repo, or comments on the commits.Sending PR's would allow
commenting on each line.
* to change the master branch we'd have to rebase all the branches and force push.

Q's
* Does this have pedagogical value?
* (core team) Should I move it to my personal github account?
* other feedback?

Steve
--
http://community.elgg.org/profile/steve_clay


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Evan Winslow  
View profile   Translate to Translated (View Original)
 More options Aug 17 2012, 12:54 pm
From: Evan Winslow <e...@elgg.org>
Date: Fri, 17 Aug 2012 09:54:22 -0700
Local: Fri, Aug 17 2012 12:54 pm
Subject: Re: [Elgg development] Teaching by git branch diffs
Print | Individual message | Show original | Report this message | Find messages by this author

Had considered teaching via example plugins. Hadn't considered doing it
with branches. Nice.

I'm fine with it under the Elgg organization account on github.

If people think this will be useful, we can advertise it via the blog. It's
also probably a good idea to link to the relevant branch from each
docs.elgg.org page and vice versa.

As for the actual content: I noticed there's a little hack you do to get
IDE's to go to CSS mode. I believe we do a similar but different thing in
core. Is there any interest in allowing .css/.js/.html files to be
recognized as views?

Evan Winslow
http://community.elgg.org/profile/ewinslow


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Brett Profitt  
View profile  
 More options Aug 20 2012, 11:57 am
From: Brett Profitt <br...@elgg.org>
Date: Mon, 20 Aug 2012 11:57:44 -0400
Local: Mon, Aug 20 2012 11:57 am
Subject: Re: [Elgg development] Teaching by git branch diffs
Print | Individual message | Show original | Report this message | Find messages by this author

> As for the actual content: I noticed there's a little hack you do to get
> IDE's to go to CSS mode. I believe we do a similar but different thing in
> core.

I use a similar hack for javascript.

> Is there any interest in allowing .css/.js/.html files to be recognized as
> views?

It could be potentially confusing because of view name vs view file
collisions. The plugin/my_view view could map to:

* mod/plugin/views/default/my_view.php
* mod/plugin/views/default/my_view.css
* mod/plugin/views/default/my_view.js
* mod/plugin/views/default/my_view.html

I raise this concern because view file locations are usually a stumbling
point for new devs. One solution could be that non PHP views require the
extension when calling: elgg_view("plugin/my_view.css"). Not sure if that's
more or less confusion for a newbie, though...

Brett

Evan Winslow

--
Brett Profitt
Elgg Lead Developer

Elgg: http://elgg.org/
Skype: brett.profitt
Twitter: http://twitter.com/brettprofitt


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google