ndlb-developers — For developers to communicate with each other.

[Ndlb-developers] uden.sherpa@gmail.com has indicated you're a friend. Accept?

[<ude...@gm...>]

Hi,

ude...@gm... wants to follow you.

****** Is ude...@gm... you friend? ******
If Yes please follow the link below:
http://invites.infoaxe.net/signup_e.html?fullname=&ema...@li...&invitername=uden&inviterid=20839092&userid=0&token=0&emailmasterid=3b655edb-b546-4635-8e22-a7f09c09d3e4&fro...@gm...&uie=0&src=txt_yes

If No please follow the link below:
http://invites.infoaxe.net/signup_e_no.html?fullname=&ema...@li...&invitername=uden&inviterid=20839092&userid=0&token=0&emailmasterid=3b655edb-b546-4635-8e22-a7f09c09d3e4&fro...@gm...&uie=0&src=txt_no


Follow the link below to remove yourself from all such emails
http://invites.infoaxe.net/uns.jsp?ema...@li...&iid=3b655edb-b546-4635-8e22-a7f09c09d3e4&fro...@gm...

[Ndlb-developers] (no subject)

[Andres M. <amo...@ga...>]

Hi Sanjay,

I am writing a small blurp of the new more robust theme support that I added
to NDLB. It was built using the plug-in theme_generator.

The way it works is that each theme may have its own stylesheets, layouts,
views, and javascripts. Please see the small article I wrote on theme
support here for a brief introduction:
http://www.gaugeus.com/ramblings/2007/11/4/adding-theme-support-to-a-ruby-on
-rails-application

These four get stored separately under the folder
/ndlb/themes/name-of-theme, which makes it very neatly compartmentalized.

The most relevant concept you should get from it is that in order to access
theme specific stylesheets and javascripts you have to use theme helpers and
in order to have customized views and layouts, you only have to follow the
same folder structure and the theme's views and layouts will automatically
override the default ones.

Relevant to what we are doing now, the new theme support, allows for
collections to have their own themes. I have created a collection called
"Centenary Celebration" and have added all of the functionality Sanjay
suggested in the design he sent me. I looks aweful, but works. Now it is up
to Sanjay to implement well the skeletal CSS and rhtml pages that I have
provided.

See http://geotourism.mobi/ndlb/

And then here:

http://geotourism.mobi/ndlb/collection/centenary-celebration

Notice how the header is different, the links etc. It no media because no
media has been added, but once it is added, it will work as it should.

The articles associated with centenary collection will be displayed on right
under About Bhutan. Below the xxx in the center panel a random picture,
video and document will be displayed that works as a link to the image,
video, and document gallery. The links above also point to the right place.

Sanjay, the theme support neatly encapsulates everything. YOU ONLY NEED TO
CHANGE what is under the ndlb\themes\centenary folder. Any image you add to
this page, you put in ndlb\themes\centenary\images. Any template you change,
you change in ndlb\themes\centenary\views, etc.

I went out of my way to have the centenary page run under NDLB but at the
same time to have its own home. Please follow the conventions so that
changes you intend for the centenary page don't break ndlb.

Sanjay, please update the CSS and rhtml with your design and commit.

I will now switch back to other urgent tasks I have for THDL. I will be
available for questions or consulting, but my contribution in terms of heavy
development is done for now; at least until it's time to fix bugs!

For the calendar, I suggest that Pema generate a calendar with the google
apps he created for e-bhutan. This allows for embedding a calendar into the
website (see settings -> Calendar details -> embed this calendar), linking
to specific events, etc. Pema, once you create a calendar in google apps,
you can assign Sanjay or whomever with read/write privileges on it and he
can take it from there.

Take care,

	Andres

Re: [Ndlb-developers] new theme support

[Pema G. <pem...@gm...>]

Hi Andres,

Great work! I am impressed with the amounts of work that is getting done in
the MMS :).

The www.e-bhutan.net.bt is still down and would be up by end of September
i.e when our Thimphu WAN will be operational.

Regards,
Pema Geyleg



On 8/23/07, Andres Montano <amo...@ga...> wrote:
>
> Hello everybody,
>
> I have added three important new features to the media management system
> (MMS):
>
> 1. Validation for existence of tables in the environment.rb file. Now it
> is
> no longer necessary to comment and uncomment stuff when doing the db
> migrations which was very annoying. If tables are not found, defaults are
> assumed.
>
> 2. Added theme support. Hopefully this will allow for seamless
> collaboration
> between THDL and NDLB. The idea is that each organization using the MMS
> can
> use its own look and feel without needed to change core code. The code
> related to look-and-feel has been isolated so that any new features added
> will be incorporated automatically to everybody using the MMS and keeping
> the integration with its own site.
>
> Tenzin, when you do an svn update in the server you have to follow some
> steps to get the appropriate theme. The steps are as follows:
>
> - svn update
> - rake db:migrate RAILS_ENV=production
> - Log into the page and go to admin section with an administrator account.
> - Under roles add all missing permissions to the administrator role.
> - Under themes select 'e-Bhutan' and update.
> - That's it!
>
> 3. Finally figured out a way to properly localize form fields. For this I
> added to the globalize_complex_scripts library the following methods:
> language_options, language_options_string, and fixed_language_options. All
> of these take one optional argument.
>
>
> The idea is that when using Rails' form helpers, so simply pass the method
> language_options and it will add the appropriate tags to the generated
> code.
> If you are not using the helpers but are coding directly in html (not
> recommended but easier for pages with a fixed language like the
> introductory
> page or help pages, use language_options_string. If a field has to accept
> Dzongkha regardless of the language (such as the search fields for media
> or
> the dictionary, or displaying "Dzongkha" in Dzongkha for language option)
> use fixed_language options. If you need to send options to the form
> helper,
> send them as arguments to the above methods and those options will be
> added.
>
> See the dictionary search page to see how it looks.
>
> Some examples.
>
> A text field that can always accept Dzongkha will look like this:
>
> <%= f.text_field :title, GlobalizeComplexScripts::fixed_language_options
> %>
>
> A text field that accepts Dzongkha only when the language is set to
> Dzongkha:
>
> <%= f.text_field :title, GlobalizeComplexScripts::language_options %>
>
> A submit button:
>
> <%= submit_tag 'Browse'.te, GlobalizeComplexScripts::language_options %>
>
> A submit button that requires the parameter "id" to be set to 'browse':
>
> <%= submit_tag 'Browse'.te, GlobalizeComplexScripts::language_options({:id
> => 'browse'}) %>
>
> The above examples are the usual case where all options are passed as one
> argument to the helper. Be mindful that some helpers have the options
> separated into options and html_options. You want to send the
> language_options to the html_options, so if you are not sending any
> options
> regarding the behavior of the object don't forget to send an empty hash
> first. For instance, a select field will look like this:
>
> <%= select(:dictionary_search, :language, @available_languages.collect
> {|l|
> [l.title.t, l.id]} + [['All languages'.t, 0]], {},
> GlobalizeComplexScripts::language_options) %>
>
> See dictionary_searches/new for samples of this code in context.
>
> Tenzin, please update the wiki with this new info.
>
> Pema, is www.e-bhutan.net.bt still down?
>
> For now the site is running here:
>
> http://geotourism.mobi/ndlb/
>
> This doesn't have any of the limitations that the development server had,
> so
> there is no problem if you want to link to it, although the URL will soon
> change to www.e-bhutan.net/ndlb .
>
> Uden, how are you doing with the fixing of links from your last task?
>
> Dechen, I updated the migrations for dictionary import. I am planning to
> soon move the dictionary import into a rake task. Having it in the
> migrations is a pain, since it takes so long (especially on a windows
> machine). The results were better with Dzongkha collation in mysql. See
>
> http://www.gaugeus.com/ramblings/2007/7/20/sorting-dzongkha-and-tibetan-unic
> ode-in-mysql-through-a-custom-collation .
>
> There are still some bugs with it, which would be great if you could fix
> with Pema.
>
> Sanjay, I have updated the Dzongkha entry page so that Dzongkha is
> rendered
> properly (using the above mentioned language_options_string) and
> converting
> all Dzongkha from Unicode characters to NCR. It would be great if you
> could
> also translate in a similar fashion (i.e. separate file for Dzongkha with
> _dz suffix) the help that pops up with the dictionary.
>
> Take care,
>
>        Andres
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> _______________________________________________
> Ndlb-developers mailing list
> Ndl...@li...
> https://lists.sourceforge.net/lists/listinfo/ndlb-developers
>

[Ndlb-developers] new theme support

[Andres M. <amo...@ga...>]

Hello everybody,

I have added three important new features to the media management system
(MMS):

1. Validation for existence of tables in the environment.rb file. Now it is
no longer necessary to comment and uncomment stuff when doing the db
migrations which was very annoying. If tables are not found, defaults are
assumed.

2. Added theme support. Hopefully this will allow for seamless collaboration
between THDL and NDLB. The idea is that each organization using the MMS can
use its own look and feel without needed to change core code. The code
related to look-and-feel has been isolated so that any new features added
will be incorporated automatically to everybody using the MMS and keeping
the integration with its own site.

Tenzin, when you do an svn update in the server you have to follow some
steps to get the appropriate theme. The steps are as follows:

- svn update
- rake db:migrate RAILS_ENV=production
- Log into the page and go to admin section with an administrator account.
- Under roles add all missing permissions to the administrator role.
- Under themes select 'e-Bhutan' and update.
- That's it!

3. Finally figured out a way to properly localize form fields. For this I
added to the globalize_complex_scripts library the following methods:
language_options, language_options_string, and fixed_language_options. All
of these take one optional argument.


The idea is that when using Rails' form helpers, so simply pass the method
language_options and it will add the appropriate tags to the generated code.
If you are not using the helpers but are coding directly in html (not
recommended but easier for pages with a fixed language like the introductory
page or help pages, use language_options_string. If a field has to accept
Dzongkha regardless of the language (such as the search fields for media or
the dictionary, or displaying "Dzongkha" in Dzongkha for language option)
use fixed_language options. If you need to send options to the form helper,
send them as arguments to the above methods and those options will be added.

See the dictionary search page to see how it looks.

Some examples.

A text field that can always accept Dzongkha will look like this:

<%= f.text_field :title, GlobalizeComplexScripts::fixed_language_options %>

A text field that accepts Dzongkha only when the language is set to
Dzongkha:

<%= f.text_field :title, GlobalizeComplexScripts::language_options %>

A submit button:

<%= submit_tag 'Browse'.te, GlobalizeComplexScripts::language_options %>

A submit button that requires the parameter "id" to be set to 'browse':

<%= submit_tag 'Browse'.te, GlobalizeComplexScripts::language_options({:id
=> 'browse'}) %>

The above examples are the usual case where all options are passed as one
argument to the helper. Be mindful that some helpers have the options
separated into options and html_options. You want to send the
language_options to the html_options, so if you are not sending any options
regarding the behavior of the object don't forget to send an empty hash
first. For instance, a select field will look like this:

<%= select(:dictionary_search, :language, @available_languages.collect {|l|
[l.title.t, l.id]} + [['All languages'.t, 0]], {},
GlobalizeComplexScripts::language_options) %>

See dictionary_searches/new for samples of this code in context.

Tenzin, please update the wiki with this new info.

Pema, is www.e-bhutan.net.bt still down?

For now the site is running here:

http://geotourism.mobi/ndlb/

This doesn't have any of the limitations that the development server had, so
there is no problem if you want to link to it, although the URL will soon
change to www.e-bhutan.net/ndlb .

Uden, how are you doing with the fixing of links from your last task?

Dechen, I updated the migrations for dictionary import. I am planning to
soon move the dictionary import into a rake task. Having it in the
migrations is a pain, since it takes so long (especially on a windows
machine). The results were better with Dzongkha collation in mysql. See
http://www.gaugeus.com/ramblings/2007/7/20/sorting-dzongkha-and-tibetan-unic
ode-in-mysql-through-a-custom-collation .

There are still some bugs with it, which would be great if you could fix
with Pema.

Sanjay, I have updated the Dzongkha entry page so that Dzongkha is rendered
properly (using the above mentioned language_options_string) and converting
all Dzongkha from Unicode characters to NCR. It would be great if you could
also translate in a similar fashion (i.e. separate file for Dzongkha with
_dz suffix) the help that pops up with the dictionary.

Take care,

	Andres

[Ndlb-developers] clean-up

[Andres M. <amo...@ga...>]

Hi Pema,

Added the rake task import:cleanup. It deletes the original picture and
movie to save space and simply not have available on the public server the
originals for people that can figure out the code.

To run simply type:

rake import:cleanup

on ndlb folder.

Take care,

	Andres

Re: [Ndlb-developers] video support

[David G. <df...@gm...>]

Dear Pema,

Great I'm hpappy this won't be delayed too long. Andres is the airplane
ticket ready to purchase?

Thanks.
david 

-----Original Message-----
From: pema geyleg [mailto:pem...@gm...] 
Sent: Sunday, June 03, 2007 5:47 AM
To: df...@gm...
Cc: Andres Montano; ndl...@li...;
ndl...@li...
Subject: Re: [Ndlb-developers] video support

Dear David,

We have filed for the visa for Andres. We should be able to get everything
done to bring Andres to Bhutan in the coming week. Andres I am looking
forward to see you soon here in Bhutan.

Pema

df...@gm... wrote:
> Andres
>
> II am very excited by this too. H owever I remain confused about the
comrpssion issue and codex issues and how this will work. We need to talk. I
am back in us by Monday noon. When are you free Monday to talk? Best for me
would be as late as possible in evening - does that work and if so at what
time? What is status of Bhutan trip?
>
> Thanks. David
> Sent via BlackBerry from T-Mobile
>
> -----Original Message-----
> From: "Andres Montano" <amo...@ga...>
>
> Date: Sun, 3 Jun 2007 02:31:47
> To:<ndl...@li...>
> Subject: [Ndlb-developers] video support
>
>
> Hi,
>
> An important update has taken place in NDLB: we have moved on from it 
> being an Image Management System to a Media Management System. Now 
> besides having pictures, it also accepts videos.
>
> All the user has to do is upload a video and the server automatically 
> does the rest (conversions, thumbnails, etc). For all of this to work 
> the proper gems and software (rmovie, rvideo, ffmpeg, and menconder) 
> should be installed on the server of course. There is a long way to go 
> here, but for now the basic functionality is there.
>
> Tenzin, you may want to change the process method under the video 
> model to the appropriate command-line instructions for it to work on
debian linux.
> Right now the commands there are what worked for windows.
>
> David, I haven't heard back from Matt nor Bess regarding the above 
> software so it doesn't work on aleph yet. What is available though is 
> playback. I have uploaded a sample generated on my development box to 
> aleph. You can find it by browsing by location to Bhumthang or 
> browsing by collection to Religion.
>
> A lot of changes have to take place like renaming some sections from 
> Images to Media, listing videos and images separately, displaying link 
> to low-res video playback, link to download video, thumbnail being the 
> middle of the video and not the beginning, etc. But at least the first 
> step, which was getting all the various pieces of technology to work, 
> was taken. Anyhow I am very excited about this. Take care,
>
> 	Andres
>
>
> ----------------------------------------------------------------------
> --- This SF.net email is sponsored by DB2 Express Download DB2 Express 
> C - the FREE version of DB2 express and take control of your XML. No 
> limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Ndlb-developers mailing list
> Ndl...@li...
> https://lists.sourceforge.net/lists/listinfo/ndlb-developers
> ----------------------------------------------------------------------
> --- This SF.net email is sponsored by DB2 Express Download DB2 Express 
> C - the FREE version of DB2 express and take control of your XML. No 
> limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Ndlb-developers mailing list
> Ndl...@li...
> https://lists.sourceforge.net/lists/listinfo/ndlb-developers
>
>   

Re: [Ndlb-developers] video support

[<df...@gm...>]

NjYNClNlbnQgdmlhIEJsYWNrQmVycnkgZnJvbSBULU1vYmlsZQ0KDQotLS0tLU9yaWdpbmFsIE1l
c3NhZ2UtLS0tLQ0KRnJvbTogcGVtYSBnZXlsZWcgPHBlbWEuZ2V5bGVnQGdtYWlsLmNvbT4NCg0K
RGF0ZTogU3VuLCAwMyBKdW4gMjAwNyAxNzo0NzoxOCANClRvOmRmZzl3d0BnbWFpbC5jb20NCkNj
OkFuZHJlcyBNb250YW5vIDxhbW9udGFub0BnYXVnZXVzLmNvbT4sIG5kbGItZGV2ZWxvcGVycy1i
b3VuY2VzQGxpc3RzLnNvdXJjZWZvcmdlLm5ldCwgbmRsYi1kZXZlbG9wZXJzQGxpc3RzLnNvdXJj
ZWZvcmdlLm5ldA0KU3ViamVjdDogUmU6IFtOZGxiLWRldmVsb3BlcnNdIHZpZGVvIHN1cHBvcnQN
Cg0KDQpEZWFyIERhdmlkLA0KDQpXZSBoYXZlIGZpbGVkIGZvciB0aGUgdmlzYSBmb3IgQW5kcmVz
LiBXZSBzaG91bGQgYmUgYWJsZSB0byBnZXQgDQpldmVyeXRoaW5nIGRvbmUgdG8gYnJpbmcgQW5k
cmVzIHRvIEJodXRhbiBpbiB0aGUgY29taW5nIHdlZWsuIEFuZHJlcyBJIA0KYW0gbG9va2luZyBm
b3J3YXJkIHRvIHNlZSB5b3Ugc29vbiBoZXJlIGluIEJodXRhbi4NCg0KUGVtYQ0KDQpkZmc5d3dA
Z21haWwuY29tIHdyb3RlOg0KPiBBbmRyZXMNCj4NCj4gSUkgYW0gdmVyeSBleGNpdGVkIGJ5IHRo
aXMgdG9vLiBIIG93ZXZlciBJIHJlbWFpbiBjb25mdXNlZCBhYm91dCB0aGUgY29tcnBzc2lvbiBp
c3N1ZSBhbmQgY29kZXggaXNzdWVzIGFuZCBob3cgdGhpcyB3aWxsIHdvcmsuIFdlIG5lZWQgdG8g
dGFsay4gSSBhbSBiYWNrIGluIHVzIGJ5IE1vbmRheSBub29uLiBXaGVuIGFyZSB5b3UgZnJlZSBN
b25kYXkgdG8gdGFsaz8gQmVzdCBmb3IgbWUgd291bGQgYmUgYXMgbGF0ZSBhcyBwb3NzaWJsZSBp
biBldmVuaW5nIC0gZG9lcyB0aGF0IHdvcmsgYW5kIGlmIHNvIGF0IHdoYXQgdGltZT8gV2hhdCBp
cyBzdGF0dXMgb2YgQmh1dGFuIHRyaXA/DQo+DQo+IFRoYW5rcy4gRGF2aWQNCj4gU2VudCB2aWEg
QmxhY2tCZXJyeSBmcm9tIFQtTW9iaWxlDQo+DQo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0t
DQo+IEZyb206ICJBbmRyZXMgTW9udGFubyIgPGFtb250YW5vQGdhdWdldXMuY29tPg0KPg0KPiBE
YXRlOiBTdW4sIDMgSnVuIDIwMDcgMDI6MzE6NDcgDQo+IFRvOjxuZGxiLWRldmVsb3BlcnNAbGlz
dHMuc291cmNlZm9yZ2UubmV0Pg0KPiBTdWJqZWN0OiBbTmRsYi1kZXZlbG9wZXJzXSB2aWRlbyBz
dXBwb3J0DQo+DQo+DQo+IEhpLA0KPg0KPiBBbiBpbXBvcnRhbnQgdXBkYXRlIGhhcyB0YWtlbiBw
bGFjZSBpbiBORExCOiB3ZSBoYXZlIG1vdmVkIG9uIGZyb20gaXQgYmVpbmcNCj4gYW4gSW1hZ2Ug
TWFuYWdlbWVudCBTeXN0ZW0gdG8gYSBNZWRpYSBNYW5hZ2VtZW50IFN5c3RlbS4gTm93IGJlc2lk
ZXMgaGF2aW5nDQo+IHBpY3R1cmVzLCBpdCBhbHNvIGFjY2VwdHMgdmlkZW9zLg0KPg0KPiBBbGwg
dGhlIHVzZXIgaGFzIHRvIGRvIGlzIHVwbG9hZCBhIHZpZGVvIGFuZCB0aGUgc2VydmVyIGF1dG9t
YXRpY2FsbHkgZG9lcw0KPiB0aGUgcmVzdCAoY29udmVyc2lvbnMsIHRodW1ibmFpbHMsIGV0Yyku
IEZvciBhbGwgb2YgdGhpcyB0byB3b3JrIHRoZSBwcm9wZXINCj4gZ2VtcyBhbmQgc29mdHdhcmUg
KHJtb3ZpZSwgcnZpZGVvLCBmZm1wZWcsIGFuZCBtZW5jb25kZXIpIHNob3VsZCBiZQ0KPiBpbnN0
YWxsZWQgb24gdGhlIHNlcnZlciBvZiBjb3Vyc2UuIFRoZXJlIGlzIGEgbG9uZyB3YXkgdG8gZ28g
aGVyZSwgYnV0IGZvcg0KPiBub3cgdGhlIGJhc2ljIGZ1bmN0aW9uYWxpdHkgaXMgdGhlcmUuDQo+
DQo+IFRlbnppbiwgeW91IG1heSB3YW50IHRvIGNoYW5nZSB0aGUgcHJvY2VzcyBtZXRob2QgdW5k
ZXIgdGhlIHZpZGVvIG1vZGVsIHRvDQo+IHRoZSBhcHByb3ByaWF0ZSBjb21tYW5kLWxpbmUgaW5z
dHJ1Y3Rpb25zIGZvciBpdCB0byB3b3JrIG9uIGRlYmlhbiBsaW51eC4NCj4gUmlnaHQgbm93IHRo
ZSBjb21tYW5kcyB0aGVyZSBhcmUgd2hhdCB3b3JrZWQgZm9yIHdpbmRvd3MuDQo+DQo+IERhdmlk
LCBJIGhhdmVuJ3QgaGVhcmQgYmFjayBmcm9tIE1hdHQgbm9yIEJlc3MgcmVnYXJkaW5nIHRoZSBh
Ym92ZSBzb2Z0d2FyZQ0KPiBzbyBpdCBkb2Vzbid0IHdvcmsgb24gYWxlcGggeWV0LiBXaGF0IGlz
IGF2YWlsYWJsZSB0aG91Z2ggaXMgcGxheWJhY2suIEkNCj4gaGF2ZSB1cGxvYWRlZCBhIHNhbXBs
ZSBnZW5lcmF0ZWQgb24gbXkgZGV2ZWxvcG1lbnQgYm94IHRvIGFsZXBoLiBZb3UgY2FuDQo+IGZp
bmQgaXQgYnkgYnJvd3NpbmcgYnkgbG9jYXRpb24gdG8gQmh1bXRoYW5nIG9yIGJyb3dzaW5nIGJ5
IGNvbGxlY3Rpb24gdG8NCj4gUmVsaWdpb24uDQo+DQo+IEEgbG90IG9mIGNoYW5nZXMgaGF2ZSB0
byB0YWtlIHBsYWNlIGxpa2UgcmVuYW1pbmcgc29tZSBzZWN0aW9ucyBmcm9tIEltYWdlcw0KPiB0
byBNZWRpYSwgbGlzdGluZyB2aWRlb3MgYW5kIGltYWdlcyBzZXBhcmF0ZWx5LCBkaXNwbGF5aW5n
IGxpbmsgdG8gbG93LXJlcw0KPiB2aWRlbyBwbGF5YmFjaywgbGluayB0byBkb3dubG9hZCB2aWRl
bywgdGh1bWJuYWlsIGJlaW5nIHRoZSBtaWRkbGUgb2YgdGhlDQo+IHZpZGVvIGFuZCBub3QgdGhl
IGJlZ2lubmluZywgZXRjLiBCdXQgYXQgbGVhc3QgdGhlIGZpcnN0IHN0ZXAsIHdoaWNoIHdhcw0K
PiBnZXR0aW5nIGFsbCB0aGUgdmFyaW91cyBwaWVjZXMgb2YgdGVjaG5vbG9neSB0byB3b3JrLCB3
YXMgdGFrZW4uIEFueWhvdyBJIGFtDQo+IHZlcnkgZXhjaXRlZCBhYm91dCB0aGlzLiBUYWtlIGNh
cmUsDQo+DQo+IAlBbmRyZXMNCj4NCj4NCj4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KPiBUaGlzIFNGLm5l
dCBlbWFpbCBpcyBzcG9uc29yZWQgYnkgREIyIEV4cHJlc3MNCj4gRG93bmxvYWQgREIyIEV4cHJl
c3MgQyAtIHRoZSBGUkVFIHZlcnNpb24gb2YgREIyIGV4cHJlc3MgYW5kIHRha2UNCj4gY29udHJv
bCBvZiB5b3VyIFhNTC4gTm8gbGltaXRzLiBKdXN0IGRhdGEuIENsaWNrIHRvIGdldCBpdCBub3cu
DQo+IGh0dHA6Ly9zb3VyY2Vmb3JnZS5uZXQvcG93ZXJiYXIvZGIyLw0KPiBfX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiBOZGxiLWRldmVsb3BlcnMgbWFp
bGluZyBsaXN0DQo+IE5kbGItZGV2ZWxvcGVyc0BsaXN0cy5zb3VyY2Vmb3JnZS5uZXQNCj4gaHR0
cHM6Ly9saXN0cy5zb3VyY2Vmb3JnZS5uZXQvbGlzdHMvbGlzdGluZm8vbmRsYi1kZXZlbG9wZXJz
DQo+IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0NCj4gVGhpcyBTRi5uZXQgZW1haWwgaXMgc3BvbnNvcmVkIGJ5
IERCMiBFeHByZXNzDQo+IERvd25sb2FkIERCMiBFeHByZXNzIEMgLSB0aGUgRlJFRSB2ZXJzaW9u
IG9mIERCMiBleHByZXNzIGFuZCB0YWtlDQo+IGNvbnRyb2wgb2YgeW91ciBYTUwuIE5vIGxpbWl0
cy4gSnVzdCBkYXRhLiBDbGljayB0byBnZXQgaXQgbm93Lg0KPiBodHRwOi8vc291cmNlZm9yZ2Uu
bmV0L3Bvd2VyYmFyL2RiMi8NCj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX18NCj4gTmRsYi1kZXZlbG9wZXJzIG1haWxpbmcgbGlzdA0KPiBOZGxiLWRldmVs
b3BlcnNAbGlzdHMuc291cmNlZm9yZ2UubmV0DQo+IGh0dHBzOi8vbGlzdHMuc291cmNlZm9yZ2Uu
bmV0L2xpc3RzL2xpc3RpbmZvL25kbGItZGV2ZWxvcGVycw0KPg0KPiAgIA0KDQo=

Re: [Ndlb-developers] video support

[pema g. <pem...@gm...>]

Dear David,

We have filed for the visa for Andres. We should be able to get 
everything done to bring Andres to Bhutan in the coming week. Andres I 
am looking forward to see you soon here in Bhutan.

Pema

df...@gm... wrote:
> Andres
>
> II am very excited by this too. H owever I remain confused about the comrpssion issue and codex issues and how this will work. We need to talk. I am back in us by Monday noon. When are you free Monday to talk? Best for me would be as late as possible in evening - does that work and if so at what time? What is status of Bhutan trip?
>
> Thanks. David
> Sent via BlackBerry from T-Mobile
>
> -----Original Message-----
> From: "Andres Montano" <amo...@ga...>
>
> Date: Sun, 3 Jun 2007 02:31:47 
> To:<ndl...@li...>
> Subject: [Ndlb-developers] video support
>
>
> Hi,
>
> An important update has taken place in NDLB: we have moved on from it being
> an Image Management System to a Media Management System. Now besides having
> pictures, it also accepts videos.
>
> All the user has to do is upload a video and the server automatically does
> the rest (conversions, thumbnails, etc). For all of this to work the proper
> gems and software (rmovie, rvideo, ffmpeg, and menconder) should be
> installed on the server of course. There is a long way to go here, but for
> now the basic functionality is there.
>
> Tenzin, you may want to change the process method under the video model to
> the appropriate command-line instructions for it to work on debian linux.
> Right now the commands there are what worked for windows.
>
> David, I haven't heard back from Matt nor Bess regarding the above software
> so it doesn't work on aleph yet. What is available though is playback. I
> have uploaded a sample generated on my development box to aleph. You can
> find it by browsing by location to Bhumthang or browsing by collection to
> Religion.
>
> A lot of changes have to take place like renaming some sections from Images
> to Media, listing videos and images separately, displaying link to low-res
> video playback, link to download video, thumbnail being the middle of the
> video and not the beginning, etc. But at least the first step, which was
> getting all the various pieces of technology to work, was taken. Anyhow I am
> very excited about this. Take care,
>
> 	Andres
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Ndlb-developers mailing list
> Ndl...@li...
> https://lists.sourceforge.net/lists/listinfo/ndlb-developers
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Ndlb-developers mailing list
> Ndl...@li...
> https://lists.sourceforge.net/lists/listinfo/ndlb-developers
>
>   

Re: [Ndlb-developers] video support

[<df...@gm...>]

QW5kcmVzDQoNCklJIGFtIHZlcnkgZXhjaXRlZCBieSB0aGlzIHRvby4gSCBvd2V2ZXIgSSByZW1h
aW4gY29uZnVzZWQgYWJvdXQgdGhlIGNvbXJwc3Npb24gaXNzdWUgYW5kIGNvZGV4IGlzc3VlcyBh
bmQgaG93IHRoaXMgd2lsbCB3b3JrLiBXZSBuZWVkIHRvIHRhbGsuIEkgYW0gYmFjayBpbiB1cyBi
eSBNb25kYXkgbm9vbi4gV2hlbiBhcmUgeW91IGZyZWUgTW9uZGF5IHRvIHRhbGs/IEJlc3QgZm9y
IG1lIHdvdWxkIGJlIGFzIGxhdGUgYXMgcG9zc2libGUgaW4gZXZlbmluZyAtIGRvZXMgdGhhdCB3
b3JrIGFuZCBpZiBzbyBhdCB3aGF0IHRpbWU/IFdoYXQgaXMgc3RhdHVzIG9mIEJodXRhbiB0cmlw
Pw0KDQpUaGFua3MuIERhdmlkDQpTZW50IHZpYSBCbGFja0JlcnJ5IGZyb20gVC1Nb2JpbGUNCg0K
LS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206ICJBbmRyZXMgTW9udGFubyIgPGFtb250
YW5vQGdhdWdldXMuY29tPg0KDQpEYXRlOiBTdW4sIDMgSnVuIDIwMDcgMDI6MzE6NDcgDQpUbzo8
bmRsYi1kZXZlbG9wZXJzQGxpc3RzLnNvdXJjZWZvcmdlLm5ldD4NClN1YmplY3Q6IFtOZGxiLWRl
dmVsb3BlcnNdIHZpZGVvIHN1cHBvcnQNCg0KDQpIaSwNCg0KQW4gaW1wb3J0YW50IHVwZGF0ZSBo
YXMgdGFrZW4gcGxhY2UgaW4gTkRMQjogd2UgaGF2ZSBtb3ZlZCBvbiBmcm9tIGl0IGJlaW5nDQph
biBJbWFnZSBNYW5hZ2VtZW50IFN5c3RlbSB0byBhIE1lZGlhIE1hbmFnZW1lbnQgU3lzdGVtLiBO
b3cgYmVzaWRlcyBoYXZpbmcNCnBpY3R1cmVzLCBpdCBhbHNvIGFjY2VwdHMgdmlkZW9zLg0KDQpB
bGwgdGhlIHVzZXIgaGFzIHRvIGRvIGlzIHVwbG9hZCBhIHZpZGVvIGFuZCB0aGUgc2VydmVyIGF1
dG9tYXRpY2FsbHkgZG9lcw0KdGhlIHJlc3QgKGNvbnZlcnNpb25zLCB0aHVtYm5haWxzLCBldGMp
LiBGb3IgYWxsIG9mIHRoaXMgdG8gd29yayB0aGUgcHJvcGVyDQpnZW1zIGFuZCBzb2Z0d2FyZSAo
cm1vdmllLCBydmlkZW8sIGZmbXBlZywgYW5kIG1lbmNvbmRlcikgc2hvdWxkIGJlDQppbnN0YWxs
ZWQgb24gdGhlIHNlcnZlciBvZiBjb3Vyc2UuIFRoZXJlIGlzIGEgbG9uZyB3YXkgdG8gZ28gaGVy
ZSwgYnV0IGZvcg0Kbm93IHRoZSBiYXNpYyBmdW5jdGlvbmFsaXR5IGlzIHRoZXJlLg0KDQpUZW56
aW4sIHlvdSBtYXkgd2FudCB0byBjaGFuZ2UgdGhlIHByb2Nlc3MgbWV0aG9kIHVuZGVyIHRoZSB2
aWRlbyBtb2RlbCB0bw0KdGhlIGFwcHJvcHJpYXRlIGNvbW1hbmQtbGluZSBpbnN0cnVjdGlvbnMg
Zm9yIGl0IHRvIHdvcmsgb24gZGViaWFuIGxpbnV4Lg0KUmlnaHQgbm93IHRoZSBjb21tYW5kcyB0
aGVyZSBhcmUgd2hhdCB3b3JrZWQgZm9yIHdpbmRvd3MuDQoNCkRhdmlkLCBJIGhhdmVuJ3QgaGVh
cmQgYmFjayBmcm9tIE1hdHQgbm9yIEJlc3MgcmVnYXJkaW5nIHRoZSBhYm92ZSBzb2Z0d2FyZQ0K
c28gaXQgZG9lc24ndCB3b3JrIG9uIGFsZXBoIHlldC4gV2hhdCBpcyBhdmFpbGFibGUgdGhvdWdo
IGlzIHBsYXliYWNrLiBJDQpoYXZlIHVwbG9hZGVkIGEgc2FtcGxlIGdlbmVyYXRlZCBvbiBteSBk
ZXZlbG9wbWVudCBib3ggdG8gYWxlcGguIFlvdSBjYW4NCmZpbmQgaXQgYnkgYnJvd3NpbmcgYnkg
bG9jYXRpb24gdG8gQmh1bXRoYW5nIG9yIGJyb3dzaW5nIGJ5IGNvbGxlY3Rpb24gdG8NClJlbGln
aW9uLg0KDQpBIGxvdCBvZiBjaGFuZ2VzIGhhdmUgdG8gdGFrZSBwbGFjZSBsaWtlIHJlbmFtaW5n
IHNvbWUgc2VjdGlvbnMgZnJvbSBJbWFnZXMNCnRvIE1lZGlhLCBsaXN0aW5nIHZpZGVvcyBhbmQg
aW1hZ2VzIHNlcGFyYXRlbHksIGRpc3BsYXlpbmcgbGluayB0byBsb3ctcmVzDQp2aWRlbyBwbGF5
YmFjaywgbGluayB0byBkb3dubG9hZCB2aWRlbywgdGh1bWJuYWlsIGJlaW5nIHRoZSBtaWRkbGUg
b2YgdGhlDQp2aWRlbyBhbmQgbm90IHRoZSBiZWdpbm5pbmcsIGV0Yy4gQnV0IGF0IGxlYXN0IHRo
ZSBmaXJzdCBzdGVwLCB3aGljaCB3YXMNCmdldHRpbmcgYWxsIHRoZSB2YXJpb3VzIHBpZWNlcyBv
ZiB0ZWNobm9sb2d5IHRvIHdvcmssIHdhcyB0YWtlbi4gQW55aG93IEkgYW0NCnZlcnkgZXhjaXRl
ZCBhYm91dCB0aGlzLiBUYWtlIGNhcmUsDQoNCglBbmRyZXMNCg0KDQotLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
DQpUaGlzIFNGLm5ldCBlbWFpbCBpcyBzcG9uc29yZWQgYnkgREIyIEV4cHJlc3MNCkRvd25sb2Fk
IERCMiBFeHByZXNzIEMgLSB0aGUgRlJFRSB2ZXJzaW9uIG9mIERCMiBleHByZXNzIGFuZCB0YWtl
DQpjb250cm9sIG9mIHlvdXIgWE1MLiBObyBsaW1pdHMuIEp1c3QgZGF0YS4gQ2xpY2sgdG8gZ2V0
IGl0IG5vdy4NCmh0dHA6Ly9zb3VyY2Vmb3JnZS5uZXQvcG93ZXJiYXIvZGIyLw0KX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCk5kbGItZGV2ZWxvcGVycyBt
YWlsaW5nIGxpc3QNCk5kbGItZGV2ZWxvcGVyc0BsaXN0cy5zb3VyY2Vmb3JnZS5uZXQNCmh0dHBz
Oi8vbGlzdHMuc291cmNlZm9yZ2UubmV0L2xpc3RzL2xpc3RpbmZvL25kbGItZGV2ZWxvcGVycw0K

[Ndlb-developers] video support

[Andres M. <amo...@ga...>]

Hi,

An important update has taken place in NDLB: we have moved on from it being
an Image Management System to a Media Management System. Now besides having
pictures, it also accepts videos.

All the user has to do is upload a video and the server automatically does
the rest (conversions, thumbnails, etc). For all of this to work the proper
gems and software (rmovie, rvideo, ffmpeg, and menconder) should be
installed on the server of course. There is a long way to go here, but for
now the basic functionality is there.

Tenzin, you may want to change the process method under the video model to
the appropriate command-line instructions for it to work on debian linux.
Right now the commands there are what worked for windows.

David, I haven't heard back from Matt nor Bess regarding the above software
so it doesn't work on aleph yet. What is available though is playback. I
have uploaded a sample generated on my development box to aleph. You can
find it by browsing by location to Bhumthang or browsing by collection to
Religion.

A lot of changes have to take place like renaming some sections from Images
to Media, listing videos and images separately, displaying link to low-res
video playback, link to download video, thumbnail being the middle of the
video and not the beginning, etc. But at least the first step, which was
getting all the various pieces of technology to work, was taken. Anyhow I am
very excited about this. Take care,

	Andres

[Ndlb-developers] streaming videos

[Andres M. <amo...@ga...>]

Hi everybody,

I am currently researching the various deployment options for video. For web
display I propose the following to resolutions:

http://people.virginia.edu/~am2zb/bhutan/

What do you think? 

Downloading the full resolution video would also be an option. These can be
generated automatically through ruby code (including the thumbnail
generation not illustrated there) and played via flash, which is how youtube
and google video work. Notice how nice this open-source player is. It also
supports synchronized captions (although I haven't checked if it is Unicode
compliant). Notice that streaming is supported which is really nice. We can
do this for all the short clips from ILCS which are the core of ritual and
have no real dialogue or narration.

Take care,

	Andres

[Ndlb-developers] [ ndlb-Bugs-1714454 ] Combo boxes are unusable

[SourceForge.net <no...@so...>]

Bugs item #1714454, was opened at 2007-05-07 17:14
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=949619&aid=1714454&group_id=194485

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Administrative Units
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Andres Montano (amontano)
Assigned to: Nobody/Anonymous (nobody)
Summary: Combo boxes are unusable

Initial Comment:
The administrative units should be chosen from some sort of hierarchical inputting system. Just having a combo box with 5000 names listed linearly doesn't really work.

This applies to anywhere where you have to choose an administrative unit such as when associating an image to a location.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=949619&aid=1714454&group_id=194485

[Ndlb-developers] ndlb

[uden s. <ude...@gm...>]

hi..
Andres i have implemented the controllers as u said with manage link that
would update with the edit, destroy and back link using ajax.

i have also implemented copyrights, copyright_holders and
reproduction_types. As you said the reproduction_types does not have
controller just model. It is populated in the migration.

i have mistakenly commited the csv files on my computer while committing the
migrations. i hope this will not be a problem Andreas.

uden

[Ndlb-developers] moving to version 0.1.2

[Andres M. <amo...@ga...>]

Hi everybody,

You may have noticed a fair amount of committals made on the last couple of
days. I have updated a couple of controllers to show how I conceive version
0.1.2 of the Image Management System should look like. It is all in the
repository, although there is no demo site to illustrate it.

David, my next task on Monday will be to follow up with Matt on the aleph
installation so that you can see a running version on a server outside of
Bhutan.

There were several issues bothering me about version 0.1.1:

1. The views were too cluttered. For instance the media index was full of
links that the average user (just browsing the page) wouldn't need and would
just confuse him. He doesn't need to see links like "associate to location"
or "add keyword". Anyhow they would just fail with a "you are not allowed to
access this function" (paraphrase) anyway.

2. The media controller was getting to loaded with stuff that didn't really
belong there.

The way I addressed these issues was with the following proposed solutions:

1. The "forbidden" links now are reduced to one: "Manage". If the average
user clicks on it, it displays an error saying "this is not for you"
(paraphrasing of course). If a user with the appropriate permissions clicks
on it, then he sees all of the extra stuff he needs to classify well the
images. The "manage" link invokes the admin action which renders the the
_admin template. To see update from svn and navigate from root via the links
"Images" -> "Browse Images" and click on any image on the right. If you
actually want to click on manage remember to use a user with the appropriate
permission. You can simply use root, but remember to update its permissions
by logging in as root and then navigating from root path via the links
"Images" -> "Manage roles" -> "System administrator" -> "Edit" -> "select
all" available roles -> ">" -> "Save changes"

2. I moved the browsing by location stuff to where it should be: the
location controller. In the media controller only remained a link to it and
the code to handle images. To see update from svn and navigate from root via
the links "Images" -> "Browse Images" -> "By Location".

Something that is still bothering me is that the main page doesn't make a
lot of sense. Next week I will ask a THDL designer called Mark to give me a
hand in making it look better and in general be arranged better.

TASKS

Tenzin, your next short-term task is then to reproduce this to allow the
user to browse by collection (put it in the
media_collection_association_controller and NOT IN collections_controller
based on what I did for the media_administrative_locations_controller),
browse by ethnicities (media_ethnicity_associations_controller), and browse
by keywords (media_keyword_associations_controller). Also implement
thematic_classifications. The new tables should be:

thematic_classifications
id
title
parent__id

media_thematic_classification_associations
id
thematic_classification_id
medium_id

The browse by thematic classifications should be placed under the
media_thematic_classification_associations_controller. The link to the
browsing should be from the media index and the link to the
associate/add/manage thematic classications should be in the media show.
(all of this is already illustrated with the new way the browsing of
administrative locations was implemented).

Uden, your next short-term task is to go through the controllers countries,
people, collections, ethnicities, and keywords and change their show action
so that instead of displaying the links "Edit | Destroy" it just displays
"Manage" which will be an ajax call to the admin action (of each controller)
that when clicked will display the "Edit | Destroy" links rendering a
"_admin" template. That way all controllers are consistent.

After you are done with this please implement the copyright related stuff
(copyrights, copyright holders, reproduction_types, organizations,
affiliations, projects, and sponsors). If you do not have the specs for
these tables I will send them to you. For all these create the migrations,
and RESTful controllers (for reproduction_types no controller is needed for
now as you should populate it directly in the migration with the following
values: no limit, prohibited, credit required, contact copyright holder).
Please make the views consistent with what we have and pay attention to
details (intuitive breadcrumbs, in the show should there a semi-colon
between the title of field and the value or not, should the title in the
field be In Mixed Case or Only with the first capitalized letter). Also be
careful for common mistakes like confusing <% and <%=.

Dechen, please adapt the sample migration to include all letters of English
to Dzongkha. Afterwards we together will proceed for the Dzongkha to English
one.

Sanjay, have you figured out a way to import images from Dept of Tourism?
Migration 36 is a sample of how you would import them tying them to a
location. A very simple change can adapt it to tying it to something else
(ethnicity, keyword, collection, thematic classification). Please figure out
a way to get as much stuff in there as possible with some way of
classification that will illustrate browsing.

Renzin, as was suggested by David, perhaps the best way to proceed now is to
install Microsoft Word on a machine and use THDL's stylesheet to mark up
texts and convert to XML. Please pick some three texts from what we have
(maybe the grammar book would be one, what do we have and which are the most
important?) and start doing this. The conversion is not perfect so you will
probably need to fix the xml afterwards. We used THDL's deep-essay for the
sample we have now but if the there aren't that many levels of headers using
the essay xslt would be enough. This means that you have to update THDL's
essay xslt files to fit into NDLB's look. Please ONLY add to the repository
what we are using. A good place to start is here:
http://www.thdl.org/xml/showEssay.php?xml=/tools/scholartools/word_to_xml.xm
l

Renzin, don't spend two weeks reading documentation. This is very simple.
Just use the THDL style sheet to mark basic stuff like Header 1, header 2,
etc.

Pema, we have to figure out a work-flow to assign somebody to go over each
picture that Sanjay will import and add as much information as possible. For
instance we can agree on some common keywords like "monk", "building",
"scenery", etc or thematic classifications like:

Building
--- Religious
----------Temple
----------Monastery
----------Chorten
--- Secular
----------Dzong

That somebody can add to the picture just by seeing it without having any
extra knowledge. Perhaps one of the translators can do this?

So Tenzin, Uden, Dechen, Sanjay, and Renzin you all have tasks now for NDLB.
Remember that we are running out of time and we need to get this rolling as
soon as possible. What I assigned to everybody shouldn't take longer than 2
or 3 days. Please check in with me constantly on any technical hurdles you
bump into.

For now, I think I am the only one sending messages to this mailing list.
Please everybody feel free to post here your thoughts and ideas and in
general any NDLB related stuff that you think is helpful for others.

We have a long way to go. What I want accomplished during May is the
following: After the Image Management System is working with all desired
functionality we will extend it to be a Media Management System and then we
put in ILCS's cool videos. Then we install Gazetteer and tie it together
with the Media Management System. Pema we can also install Sakai for news,
forums, etc. For the wiki we should stick to what we already have and it is
possible to link sakai with other wikis. Once we have all of these pieces of
the puzzle put together then we will have something very impressive to show.
But we have to work diligently and give it high-priority for us to get it
done on time.

Everybody take care,

	Andres

[Ndlb-developers] ruby on rails running as an off-line app

[Andres M. <amo...@ga...>]

Hi,

Take a look at:

http://developers.joyent.com/

They offer a way to make a ruby on rails app run as an off-line application
(that even synchronizes with the on-line one). Worth looking into.

Take care,

	Andres

[Ndlb-developers] on svn mailing list

[Andres M. <amo...@ga...>]

Hi Guys,

Now that the svn repository is fully up-to-date and everybody's accounts are
working I will go over the code, quickly correcting stuff to take it to
release 0.1.1 and make a plan on how to move forward to release 0.2. 

The svn mailing list seems to work well as it is relaying all commits made.
Please take the time to skim through it and read the logs carefully as I am
making an effort to write descriptive messages giving the reasons for the
changes and whenever relevant defining a convention or standard on how to
deal with recurring cases for all of us to follow.

Remember that one of the advantages of Ruby on Rails' "convention of
configuration" is that it is easy to debug since you can easily infer where
to find stuff. Of course this only works when we actually follow the
conventions and although this applies to one developer "not forgetting"
where he did his thing all the more it applies with collaborative
development.

In order to avoid getting a bunch of little messages I have changed the
default for everybody in the svn mailing list to digest. You can always
change it back if you prefer to receive the messages individually.

Take care,

	Andres

[Ndlb-developers] on the ndlb-svn list

[Andres M. <amo...@ga...>]

Hi,

In order for the svn commit trigger to post the message into the ndlb-svn
list the mailing list you have to register your sourceforge redirect
"e-mail" into it, which is your user name plus @users.sourceforge.net. I
registered Pema, Sanjay, and Tenzin's e-mail because I knew their sf
accounts.

Uden, Dechen, and Renzin, once you create your accounts and either me or
Pema adds you as developers, please register to the ndlb-svn mailing list.
Remember to use your sf account + @users.sourceforge.net (NOT your gmail
account).

Thanks,

	Andres

[Ndlb-developers] ndlb project is now set on source forge

[Andres M. <amo...@gm...>]

Hi guys,

We will use this e-mail for all development related communications so that a
log is kept.

Right now Pema, Sanjay, Tenzin, and me are on it, since those were the only
source forge accounts I knew. For now Pema and I are the project
administrators. Pema, I leave it up to you if you want to give administrator
privileges to others. Sanjay and Tenzin I put as developers.

Dechen, Uden, and Rinzin, please send either me or Pema your source forge
account, or to create one if you don't have ( http://sf.net ). Either Pema
or I can add you as developers. 

I have uploaded the Ruby on Rails code to an svn repository at source-forge
and I have added a hook to send the commit diffs and comments to ndlb-svn.

Only source code is there; no data at all (so when running the migrations
data has to be copied into the migration folders separately, such as the
dictionary files, the pictures, etc.). This takes care of the issues of
privacy. Since the project started from the beginning in the spirit of GPL,
I consider that it is ok for other people to look at it; regardless, I
consider very few people will since there is so much stuff out there and it
we aren't developing a general-use application, but something tailored for
our specific needs.

The repository is organized like this:

   portal
     |
    ror
   /   \
tags   trunk

All web applications should be under "portal". The off-line tools that we
develop would be in another folder. Under "ror" is the Ruby on Rails
application that will be only one (all new modules will be subsumed under
one big RoR application). Web applications developed under other platforms
would still be under portal but not under "ror". "trunk" has the edge code
where we commit the new code and "tags" has stable versions marking the
various phases that we will reach in time. We are currently at release 0.1!

The production server should check-out from:
https://ndlb.svn.sourceforge.net/svnroot/ndlb/portal/ror/tags/release-0.1

And with each new release a switch to it should be run on the server's
working copy.

The development machines should check-out from:
https://ndlb.svn.sourceforge.net/svnroot/ndlb/portal/ror/trunk

Please check out a fresh copy. In eclipse do file -> new -> project... ->
SVN -> Check Projects from SVN -> Create new repository location ->
https://ndlb.svn.sourceforge.net/svnroot/ndlb -> and then browse to
portal/ror/trunk -> Check out as project in workspace -> project name
"ndlb". 

the svn location you can write https://ndlb.svn.sourceforge.net/svnroot/ndlb
and then

A lot of files have been revised, including all migrations. Remember to fix
the config/database.yml with the appropriate socket, user, and password (for
linux it is probably much faster to connect via socket instead of host).

If you don't have the mysql databases you should create them
(ndlb_development, _test, and _production) with utf8 as default character
set (create database ndlb_development default character set utf8;) as well a
the user to connect to it (grant all on ndlb_%.* to rubyuser@'localhost'
identified by 'rubypassword';). For the new database you should run:

% rake globalize:setup

And for the other two environments as well (rake globalize:setup
RAILS_ENV=test, rake globalize:setup RAILS_ENV=production)

If you already have a database, try "rake db:migrate VERSION=0" to drop all
tables (except the globalize tables which where not created by the
migration, but by the above statement; so in the server we won't loose the
translated messages).

Then after commenting the stuff under "Code for globalization" in
config/environment.rb and adding the extra files (for the data importation,
see below) run:

% rake db:migrate

(also for the other two environments as well: rake db:migrate
RAILS_ENV=test, and rake db:migrate RAILS_ENV=production).

And then uncomment those lines again. Copy into the new project any files
that you have modified and revise them running right-click -> compare with
-> latest from repository and do the necessary changes. Then commit them.
After all of us are on the same page and all code that we have done is there
we can assess were we are and make a plan on how to move forward.

Pema, I will write a separate e-mail to keep you up to date on what we
discussed on the various meetings at the University of Virginia in my latest
visit.

Sanjay, I will send you the CSV with the location names that worked for the
migration

Dechen, I will send you the three sample dictionary files that worked with
the migration, so that you can add all letters to the English to Dzongkha
dictionary.

Again all data I will send separately so that it is not in source forge (nor
in the mailing lists).

For the images, under db\migrate\images create folders with the names of
places (exactly matching what was imported for location names) and on those
folders put the images that should be associated to that place. DO NOT
create a tree structure there, only the name of the folder for the district,
village, or block where the picture should be at the first level.

Rinzin, the xml and xslt files we will not put under portal/ror. Let me
figure out were we will put them and then let you know.

Take care and let me know when you have updated the svn server with the
latest code for me to revise and then we can move forward,

	Andres