You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bloodhound.apache.org by Ryan Ollos <ry...@wandisco.com> on 2014/03/10 16:30:03 UTC
Re: GSOC 2014 -- Dynamic calendar and scheduling tools for the
Bloodhound issue tracker
On Mon, Mar 10, 2014 at 2:23 AM, Ryan Ollos <ry...@wandisco.com> wrote:
> On Mon, Mar 10, 2014 at 2:02 AM, Devender <de...@gmail.com>wrote:
>
>> Hi Ryan,
>>
>> I am a 4th year student of the Department of Computer Science and
>> Engineering at Indian Institute of Technology( IIT), Kharagpur, India.
>>
>> I am good at programming in Python, AJAX, PHP, MySQL, JavaScript,
>> jQuery, HTML, CSS and C++. I have worked on projects which used python
>> and web development technologies.
>>
>> I am very enthusiast to work with Apache in GSOC 2014. I have installed
>> and used the bloodhound and I am interested to work on this idea (
>> COMDEV-112 <https://issues.apache.org/jira/browse/COMDEV-112>). I have
>> done setup for the basic development environment for Bloodhound. I have
>> been looking at the starter ticket<https://issues.apache.org/bloodhound/query?status=!closed&keywords=~starter>
>> *,* but I don't know which ticket I should work on. Please guide me to
>> proceed for my proposal.
>>
>
> Hi Devender,
>
> Welcome!
>
> It might be good to familiarize yourself with Bootstrap by working ticket
> #570 (1). To get started,
> 1. Review the Bootstrap 2.3 documents
> 2. Copy the template
> bloodhound_multiproduct/multiproduct/templates/product_edit.html to
> bloodhound_theme/bhtheme/templates/bh_product_edit.html
> 3. Add bh_product_edit.html to the template map in
> bloodhound_theme/bhtheme/theme.py
> 4. Modify the markup in the template so that we get nice styling on
> multiple devices (desktop, tablet, mobile).
>
> You can study the other templates in bloodhound_theme to learn how the
> Boostrap markup can be used.
>
> For the COMDEV-112 project, it is a bit open-ended, which gives you a lot
> of room to work with the community to define the solution. You can get
> started by looking at the architecture of the plugins mentioned in #766 (3).
>
> (1) https://issues.apache.org/bloodhound/ticket/570
> (2) http://getbootstrap.com/2.3.2/
> (3) https://issues.apache.org/bloodhound/ticket/766
>
>
Devender, I didn't notice initially that you sent the email directly to me.
This is just a quick note to say that future emails should be directed to
the dev@bloodhound.apache.org list, which I've added to the Reply of this
email. This is to keep the whole Bloodhound community involved in your
project :)
Re: GSOC 2014 -- Dynamic calendar and scheduling tools for the
Bloodhound issue tracker
Posted by Devender <de...@gmail.com>.
Hi Gary,
I have added those images to my proposal https://issues.apache.org/
bloodhound/wiki/Proposals/BEP-0015. Please provide your feedback.
Devender (Linkedin
Profile<http://in.linkedin.com/pub/devender-bindal/27/70b/133/>
)
4th Year Student
Dual Degree(B.Tech+M.Tech)
Computer Science and Engineering
IIT Kharagpur
Phone +91-8967224480
Alternate Email *devender@cse.iitkgp.ernet.in
<de...@cse.iitkgp.ernet.in>*
On Fri, Mar 21, 2014 at 3:41 PM, Gary Martin <ga...@wandisco.com>wrote:
> Hi Devender,
>
>
> 2. Creation of wire frames to showing envision of the features to be
>> presented.
>>
>> I suggest two wireframes design:
>>
>> i. When user click on the calendar tab, calendar content will be shown.
>> (calendar.png) but when user is in query page or milestone page and if it
>> click on the calendar tab. The calendar layout will be appended to it in
>> the bottom on that page itself by using jquery tabs. This layout will make
>> drag n drop easy to implement as user can drag any ticket or milestone and
>> drop on the calendar.(milestone_with_calendar.png and
>> query_page_with_calendar.png).
>>
>> ii. When user click on the calendar tab, calendar content will be shown.
>> (calendar.png) and for the milestone and query page, when user click on
>> the
>> pop-up will be open with the calendar view(popup_milestone.png and
>> popup_querypage.png). User can click on the calendar and to drag and drop,
>> user drag any ticket and drop on the calendar.
>>
>> Please suggest which one is better or any new approach so that I can
>> change
>> my proposal.
>>
>>
> Did you mean to attach images to your email as that might have failed. If
> the four images you created are available, you might want to attach them
> all to https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0015 to
> allow us to view them.
>
> Cheers,
> Gary
>
Re: GSOC 2014 -- Dynamic calendar and scheduling tools for the Bloodhound
issue tracker
Posted by Gary Martin <ga...@wandisco.com>.
Hi Devender,
> 2. Creation of wire frames to showing envision of the features to be
> presented.
>
> I suggest two wireframes design:
>
> i. When user click on the calendar tab, calendar content will be shown.
> (calendar.png) but when user is in query page or milestone page and if it
> click on the calendar tab. The calendar layout will be appended to it in
> the bottom on that page itself by using jquery tabs. This layout will make
> drag n drop easy to implement as user can drag any ticket or milestone and
> drop on the calendar.(milestone_with_calendar.png and
> query_page_with_calendar.png).
>
> ii. When user click on the calendar tab, calendar content will be shown.
> (calendar.png) and for the milestone and query page, when user click on the
> pop-up will be open with the calendar view(popup_milestone.png and
> popup_querypage.png). User can click on the calendar and to drag and drop,
> user drag any ticket and drop on the calendar.
>
> Please suggest which one is better or any new approach so that I can change
> my proposal.
>
Did you mean to attach images to your email as that might have failed.
If the four images you created are available, you might want to attach
them all to https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0015
to allow us to view them.
Cheers,
Gary
Re: GSOC 2014 -- Dynamic calendar and scheduling tools for the
Bloodhound issue tracker
Posted by Devender <de...@gmail.com>.
Hi Ryan,
I am working on two points as discussed on IRC :
1. How to modified the existing plugins in order to work with bloodhound to
implement the calendar view and other features.
i. Add Basic feature of month-long calendar view, showing the due date for
milestone and tickets
As bloodhound extends trac and it allow multiproduct support and good
interface with bootstrap. To use the existing trac ticket calendar plugin,
a. initially use this template(1) and add the bootstrap support,
b. then add the multiproduct support.(I need some help on this a and b
point)
ii. Add Several filters like filter by user, milestone, open/close ticket,
sort by priority asc/desc, reopened, status, assigned.
For this above a and b remain same but then to add any more filter i.e
product filter will be added to above plugin.
iii. Add Drag and drop feature for the schedule ticket onto the calendar
view.
yes that trac drag and drop(2) cannot be used, So I am thinking of starting
it with the jquery plugin but they will be use as example purpose for the
implementation.
iv. Scale the view: week, month, year.
Previous I mentioned to use the trac week plan plugin(3) but I think this
plugin need to significantly modify for our purpose because of no support
for ticket and milestone. So, I am thinking, when the above basic month
view will be done, then that calendar will be modified to create this week
and year view.So it will be like calendar view containing three view: year,
month and week with month view as default.
Please provide feedback about these points so that I can modify my proposal
as soon as possible.
2. Creation of wire frames to showing envision of the features to be
presented.
I suggest two wireframes design:
i. When user click on the calendar tab, calendar content will be shown.
(calendar.png) but when user is in query page or milestone page and if it
click on the calendar tab. The calendar layout will be appended to it in
the bottom on that page itself by using jquery tabs. This layout will make
drag n drop easy to implement as user can drag any ticket or milestone and
drop on the calendar.(milestone_with_calendar.png and
query_page_with_calendar.png).
ii. When user click on the calendar tab, calendar content will be shown.
(calendar.png) and for the milestone and query page, when user click on the
pop-up will be open with the calendar view(popup_milestone.png and
popup_querypage.png). User can click on the calendar and to drag and drop,
user drag any ticket and drop on the calendar.
Please suggest which one is better or any new approach so that I can change
my proposal.
(1)
https://trac-hacks.org/browser/ticketcalendarplugin/0.12/ticketcalendar/templates
(2) http://trac-hacks.org/wiki/TracDragDropPlugin
(3) https://trac-hacks.org/wiki/WeekPlanPlugin
On Thu, Mar 20, 2014 at 9:36 PM, Devender <de...@gmail.com> wrote:
> Hi Ryan,
>
> I have added a draft of the proposal on wiki (1). Please provide your
> feedback.
>
> (1) https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0015
>
> Devender (Linkedin Profile<http://in.linkedin.com/pub/devender-bindal/27/70b/133/>
> )
> 4th Year Student
> Dual Degree(B.Tech+M.Tech)
> Computer Science and Engineering
> IIT Kharagpur
> Phone +91-8967224480
> Alternate Email *devender@cse.iitkgp.ernet.in
> <de...@cse.iitkgp.ernet.in>*
>
>
> On Thu, Mar 20, 2014 at 8:23 PM, Ryan Ollos <ry...@wandisco.com>wrote:
>
>> Hi Devender,
>>
>> You may use BEP-0015:
>> https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0015
>>
>> I will take a look at your proposal and should be on IRC 2 hours from now.
>>
>>
>>
>> On Thu, Mar 20, 2014 at 2:40 AM, Devender <de...@gmail.com>wrote:
>>
>>> Hi Ryan,
>>>
>>> I have submitted my proposal to GSOC 2014 website(1). Please provide
>>> feedback. I want to submit on the wiki page, please create a page.
>>>
>>> (1)
>>> https://www.google-melange.com/gsoc/proposal/public/google/gsoc2014/devenderbindal/5629499534213120
>>>
>>>
>>> On Thu, Mar 20, 2014 at 8:35 AM, Devender <de...@gmail.com>wrote:
>>>
>>>> In previous mail, I forgot to direct to dev@bloodhound.apache.org. So
>>>>
>>>>
>>>> On Thu, Mar 20, 2014 at 8:26 AM, Devender <de...@gmail.com>wrote:
>>>>
>>>>> Hi Ryan,
>>>>>
>>>>> I have submit a patch for ticket 570.(1) Please provide your feedback
>>>>> about it. I have a doubt about this patch I want to discuss on IRC. Other
>>>>> than that I have to discuss some points about the proposal. What time can I
>>>>> catch you on IRC?
>>>>>
>>>>>
>>>>> https://github.com/dev9226134/bloodhound/commit/0b9c57943a4e98b569eea7185962186153fbea08
>>>>>
>>>>>
>>>>> On Tue, Mar 18, 2014 at 3:44 AM, Ryan Ollos <ry...@wandisco.com>wrote:
>>>>>
>>>>>> On Thu, Mar 13, 2014 at 3:01 AM, Devender <de...@gmail.com>wrote:
>>>>>>
>>>>>>> Hi Ryan,
>>>>>>>
>>>>>>> I have been working on the proposal. I have mentioned some points
>>>>>>> about the given 6 features. Please provide your feedback on point given
>>>>>>> below, So that I can come with the concise sub-feature set in these 6
>>>>>>> features:
>>>>>>>
>>>>>>> 1.To add basic feature of a month-long calendar view of a
>>>>>>> milestone, showing the milestone due date and due date for tickets
>>>>>>> As given in the ticket #766 (1) we can use the modified trac ticket
>>>>>>> calender plugin (2), I have installed and tried this plugin.
>>>>>>> or
>>>>>>> we can develop the calender view from scratch using basic web
>>>>>>> development and combine it with the bootstrap to make it look beautiful.
>>>>>>>
>>>>>>> Also we can also extend the calender view to google calender as a
>>>>>>> different plugin in addition to the above plugin (4) but it will be
>>>>>>> requiring the internet and it is not open source.
>>>>>>>
>>>>>>
>>>>>> Utilizing one of the existing plugins as a starting point seems like
>>>>>> the best choice. If you need to significantly modify it or rewrite parts of
>>>>>> the plugin later to fit your needs, then the project can progress in that
>>>>>> direction.
>>>>>>
>>>>>> With regard to Google Calendar, I suppose it would be possible to
>>>>>> embed a Google Calendar view (or another similar 3rd party calendar into
>>>>>> Bloodhound). What I would consider doing instead though, is allowing a user
>>>>>> of Google Calendar to subscribe to the Bloodhound calendar. This would use
>>>>>> the iCAL or CALDav format. Google Calendar at least supports the iCAL
>>>>>> format, and you can subscribe to any calendar that is provided in that
>>>>>> format. I'm not sure if it supports CALDav (and I wasn't even aware of this
>>>>>> format until Gary mentioned it a few weeks back, so we'd need to
>>>>>> investigate what use cases it could support).
>>>>>>
>>>>>> You might want to consider the "calendar subscription" feature to be
>>>>>> implemented later in the project, if time allows. It doesn't have to be
>>>>>> part of the primary deliverable that you are aiming for, but you could
>>>>>> suggest it as an extra feature that will be added if time allows.
>>>>>>
>>>>>>
>>>>>>> 2. To Allow tickets to be scheduled by drag 'n drop onto the
>>>>>>> calendar view.
>>>>>>> First I can make the tickets "div draggable true" and then I can add
>>>>>>> the basic javascript function (7) i.e what to drag, where to drop and do
>>>>>>> the drop.
>>>>>>> or
>>>>>>> I can use jquery plugin (5).
>>>>>>>
>>>>>>
>>>>>> This sounds good. There are some examples on trac-hacks that you can
>>>>>> look at to see how the drag and drop functionality might be implemented.
>>>>>> For example,
>>>>>> http://trac-hacks.org/wiki/TracDragDropPlugin
>>>>>> http://trac-hacks.org/wiki/QueuesPlugin
>>>>>>
>>>>>>
>>>>>>> 3. To Scale the view: week, month, year.
>>>>>>> There is another library mentioned in the ticket #766 as trac week
>>>>>>> plan plugin (3), I have installed and tried this plugin as well. I can
>>>>>>> extend this plugin to the month calender as sub plugin and I can create the
>>>>>>> year plugin similarly as well. So, It will be like calender view containing
>>>>>>> three view: year, month, and week with month view as default.
>>>>>>>
>>>>>>> 4. To add Filters for the calendar view. For example: filter by
>>>>>>> user, milestone, open/closed tickets.
>>>>>>> trac calender plugin also contain several filter which are required
>>>>>>> or If created alone, then also these filters can be done by simple database
>>>>>>> queries.
>>>>>>>
>>>>>>> 5. To Embed the calendar views in the query page and milestone
>>>>>>> pages.
>>>>>>> I can put a button in query and milestone page and when user click
>>>>>>> the button
>>>>>>> this will add the calender to the right side to the existing page by
>>>>>>> using jquery. or It will go to the calender page or I can add some
>>>>>>> indexing based on the jquery tab (6).
>>>>>>>
>>>>>>
>>>>>> I think you have the right idea. Since the milestone view page
>>>>>> currently displays a table of tickets - the result of a ticket query for
>>>>>> the milestone - another possibility is to allow the user to toggle between
>>>>>> the ticket query table and calendar views.
>>>>>>
>>>>>>
>>>>>>> 6. Allow the calendar to be annotated with arbitrary notes/events
>>>>>>> that do not represent tickets.
>>>>>>> a new class can be added to the existing trac plugins to support any
>>>>>>> note feature,
>>>>>>> these note can be off different color from ticket/milestones.
>>>>>>>
>>>>>>
>>>>>> You seem to have a good grasp of the project. If you want to discuss
>>>>>> details further, feel free to reply, or else you can catch me on IRC. I'll
>>>>>> try to be frequently available on IRC over the next several days.
>>>>>>
>>>>>
>>>>> Hi Devender,
>>>>
>>>> I copied over the file you'll need to start with in r1578595 and
>>>> r1578599 (1, 2). Now we have
>>>> bloodhound_theme/bhtheme/templates/bh_product_edit.html which needs to be
>>>> modified for Bootstrap markup. This consists of basic things like adding
>>>> the "btn" class to inputs of type "submit", and adding the "row" and "span"
>>>> classes to divs. To learn the markup, you can compare templates between
>>>> Trac and Bloodhound. For example, you can diff
>>>> bloodhound_theme/bhtheme/templates/bh_report_list.html and
>>>> trac/trac/ticket/templates/report_list.html.
>>>>
>>>> The BloodhoundTheme templates are not perfect. Please let us know if
>>>> you spot any inconsistencies or issues on certain platforms or devices.
>>>>
>>>> You can take a look at the recent messages sent to Thimal (3) to get
>>>> additional pointers. He worked on the template for the Roadmap page, which
>>>> was committed over the weekend (4). The changes you'll need to make are
>>>> similar to those made for the Roadmap. Again, it would be good to look at
>>>> the diffs. You can also view the diffs through the links I sent to Apache
>>>> ViewVC (which aren't the nicest to view), through your client-side tool or
>>>> on GitHub (5). For example, the complementary link to (4) on GitHub is (6).
>>>>
>>>> (1) http://svn.apache.org/viewvc?view=revision&revision=r1578595
>>>> (2) http://svn.apache.org/viewvc?view=revision&revision=r1578599
>>>> (3) http://apache.markmail.org/thread/rnwh5jz3tvxi6kz2
>>>> (4) http://svn.apache.org/viewvc?view=revision&revision=r1578223
>>>> (5) https://github.com/apache/bloodhound/commits/trunk
>>>> (6)
>>>> https://github.com/apache/bloodhound/commit/5d412c09151c080f826dc595b79e670dc62be7a8
>>>>
>>>>
>>>
>>
>
Re: GSOC 2014 -- Dynamic calendar and scheduling tools for the
Bloodhound issue tracker
Posted by Devender <de...@gmail.com>.
Hi Ryan,
I have added a draft of the proposal on wiki (1). Please provide your
feedback.
(1) https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0015
Devender (Linkedin
Profile<http://in.linkedin.com/pub/devender-bindal/27/70b/133/>
)
4th Year Student
Dual Degree(B.Tech+M.Tech)
Computer Science and Engineering
IIT Kharagpur
Phone +91-8967224480
Alternate Email *devender@cse.iitkgp.ernet.in
<de...@cse.iitkgp.ernet.in>*
On Thu, Mar 20, 2014 at 8:23 PM, Ryan Ollos <ry...@wandisco.com> wrote:
> Hi Devender,
>
> You may use BEP-0015:
> https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0015
>
> I will take a look at your proposal and should be on IRC 2 hours from now.
>
>
>
> On Thu, Mar 20, 2014 at 2:40 AM, Devender <de...@gmail.com>wrote:
>
>> Hi Ryan,
>>
>> I have submitted my proposal to GSOC 2014 website(1). Please provide
>> feedback. I want to submit on the wiki page, please create a page.
>>
>> (1)
>> https://www.google-melange.com/gsoc/proposal/public/google/gsoc2014/devenderbindal/5629499534213120
>>
>>
>> On Thu, Mar 20, 2014 at 8:35 AM, Devender <de...@gmail.com>wrote:
>>
>>> In previous mail, I forgot to direct to dev@bloodhound.apache.org. So
>>>
>>>
>>> On Thu, Mar 20, 2014 at 8:26 AM, Devender <de...@gmail.com>wrote:
>>>
>>>> Hi Ryan,
>>>>
>>>> I have submit a patch for ticket 570.(1) Please provide your feedback
>>>> about it. I have a doubt about this patch I want to discuss on IRC. Other
>>>> than that I have to discuss some points about the proposal. What time can I
>>>> catch you on IRC?
>>>>
>>>>
>>>> https://github.com/dev9226134/bloodhound/commit/0b9c57943a4e98b569eea7185962186153fbea08
>>>>
>>>>
>>>> On Tue, Mar 18, 2014 at 3:44 AM, Ryan Ollos <ry...@wandisco.com>wrote:
>>>>
>>>>> On Thu, Mar 13, 2014 at 3:01 AM, Devender <de...@gmail.com>wrote:
>>>>>
>>>>>> Hi Ryan,
>>>>>>
>>>>>> I have been working on the proposal. I have mentioned some points
>>>>>> about the given 6 features. Please provide your feedback on point given
>>>>>> below, So that I can come with the concise sub-feature set in these 6
>>>>>> features:
>>>>>>
>>>>>> 1.To add basic feature of a month-long calendar view of a milestone,
>>>>>> showing the milestone due date and due date for tickets
>>>>>> As given in the ticket #766 (1) we can use the modified trac ticket
>>>>>> calender plugin (2), I have installed and tried this plugin.
>>>>>> or
>>>>>> we can develop the calender view from scratch using basic web
>>>>>> development and combine it with the bootstrap to make it look beautiful.
>>>>>>
>>>>>> Also we can also extend the calender view to google calender as a
>>>>>> different plugin in addition to the above plugin (4) but it will be
>>>>>> requiring the internet and it is not open source.
>>>>>>
>>>>>
>>>>> Utilizing one of the existing plugins as a starting point seems like
>>>>> the best choice. If you need to significantly modify it or rewrite parts of
>>>>> the plugin later to fit your needs, then the project can progress in that
>>>>> direction.
>>>>>
>>>>> With regard to Google Calendar, I suppose it would be possible to
>>>>> embed a Google Calendar view (or another similar 3rd party calendar into
>>>>> Bloodhound). What I would consider doing instead though, is allowing a user
>>>>> of Google Calendar to subscribe to the Bloodhound calendar. This would use
>>>>> the iCAL or CALDav format. Google Calendar at least supports the iCAL
>>>>> format, and you can subscribe to any calendar that is provided in that
>>>>> format. I'm not sure if it supports CALDav (and I wasn't even aware of this
>>>>> format until Gary mentioned it a few weeks back, so we'd need to
>>>>> investigate what use cases it could support).
>>>>>
>>>>> You might want to consider the "calendar subscription" feature to be
>>>>> implemented later in the project, if time allows. It doesn't have to be
>>>>> part of the primary deliverable that you are aiming for, but you could
>>>>> suggest it as an extra feature that will be added if time allows.
>>>>>
>>>>>
>>>>>> 2. To Allow tickets to be scheduled by drag 'n drop onto the
>>>>>> calendar view.
>>>>>> First I can make the tickets "div draggable true" and then I can add
>>>>>> the basic javascript function (7) i.e what to drag, where to drop and do
>>>>>> the drop.
>>>>>> or
>>>>>> I can use jquery plugin (5).
>>>>>>
>>>>>
>>>>> This sounds good. There are some examples on trac-hacks that you can
>>>>> look at to see how the drag and drop functionality might be implemented.
>>>>> For example,
>>>>> http://trac-hacks.org/wiki/TracDragDropPlugin
>>>>> http://trac-hacks.org/wiki/QueuesPlugin
>>>>>
>>>>>
>>>>>> 3. To Scale the view: week, month, year.
>>>>>> There is another library mentioned in the ticket #766 as trac week
>>>>>> plan plugin (3), I have installed and tried this plugin as well. I can
>>>>>> extend this plugin to the month calender as sub plugin and I can create the
>>>>>> year plugin similarly as well. So, It will be like calender view containing
>>>>>> three view: year, month, and week with month view as default.
>>>>>>
>>>>>> 4. To add Filters for the calendar view. For example: filter by
>>>>>> user, milestone, open/closed tickets.
>>>>>> trac calender plugin also contain several filter which are required
>>>>>> or If created alone, then also these filters can be done by simple database
>>>>>> queries.
>>>>>>
>>>>>> 5. To Embed the calendar views in the query page and milestone pages.
>>>>>>
>>>>>> I can put a button in query and milestone page and when user click
>>>>>> the button
>>>>>> this will add the calender to the right side to the existing page by
>>>>>> using jquery. or It will go to the calender page or I can add some
>>>>>> indexing based on the jquery tab (6).
>>>>>>
>>>>>
>>>>> I think you have the right idea. Since the milestone view page
>>>>> currently displays a table of tickets - the result of a ticket query for
>>>>> the milestone - another possibility is to allow the user to toggle between
>>>>> the ticket query table and calendar views.
>>>>>
>>>>>
>>>>>> 6. Allow the calendar to be annotated with arbitrary notes/events
>>>>>> that do not represent tickets.
>>>>>> a new class can be added to the existing trac plugins to support any
>>>>>> note feature,
>>>>>> these note can be off different color from ticket/milestones.
>>>>>>
>>>>>
>>>>> You seem to have a good grasp of the project. If you want to discuss
>>>>> details further, feel free to reply, or else you can catch me on IRC. I'll
>>>>> try to be frequently available on IRC over the next several days.
>>>>>
>>>>
>>>> Hi Devender,
>>>
>>> I copied over the file you'll need to start with in r1578595 and
>>> r1578599 (1, 2). Now we have
>>> bloodhound_theme/bhtheme/templates/bh_product_edit.html which needs to be
>>> modified for Bootstrap markup. This consists of basic things like adding
>>> the "btn" class to inputs of type "submit", and adding the "row" and "span"
>>> classes to divs. To learn the markup, you can compare templates between
>>> Trac and Bloodhound. For example, you can diff
>>> bloodhound_theme/bhtheme/templates/bh_report_list.html and
>>> trac/trac/ticket/templates/report_list.html.
>>>
>>> The BloodhoundTheme templates are not perfect. Please let us know if you
>>> spot any inconsistencies or issues on certain platforms or devices.
>>>
>>> You can take a look at the recent messages sent to Thimal (3) to get
>>> additional pointers. He worked on the template for the Roadmap page, which
>>> was committed over the weekend (4). The changes you'll need to make are
>>> similar to those made for the Roadmap. Again, it would be good to look at
>>> the diffs. You can also view the diffs through the links I sent to Apache
>>> ViewVC (which aren't the nicest to view), through your client-side tool or
>>> on GitHub (5). For example, the complementary link to (4) on GitHub is (6).
>>>
>>> (1) http://svn.apache.org/viewvc?view=revision&revision=r1578595
>>> (2) http://svn.apache.org/viewvc?view=revision&revision=r1578599
>>> (3) http://apache.markmail.org/thread/rnwh5jz3tvxi6kz2
>>> (4) http://svn.apache.org/viewvc?view=revision&revision=r1578223
>>> (5) https://github.com/apache/bloodhound/commits/trunk
>>> (6)
>>> https://github.com/apache/bloodhound/commit/5d412c09151c080f826dc595b79e670dc62be7a8
>>>
>>>
>>
>
Re: GSOC 2014 -- Dynamic calendar and scheduling tools for the
Bloodhound issue tracker
Posted by Ryan Ollos <ry...@wandisco.com>.
Hi Devender,
You may use BEP-0015:
https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0015
I will take a look at your proposal and should be on IRC 2 hours from now.
On Thu, Mar 20, 2014 at 2:40 AM, Devender <de...@gmail.com> wrote:
> Hi Ryan,
>
> I have submitted my proposal to GSOC 2014 website(1). Please provide
> feedback. I want to submit on the wiki page, please create a page.
>
> (1)
> https://www.google-melange.com/gsoc/proposal/public/google/gsoc2014/devenderbindal/5629499534213120
>
>
> On Thu, Mar 20, 2014 at 8:35 AM, Devender <de...@gmail.com>wrote:
>
>> In previous mail, I forgot to direct to dev@bloodhound.apache.org. So
>>
>>
>> On Thu, Mar 20, 2014 at 8:26 AM, Devender <de...@gmail.com>wrote:
>>
>>> Hi Ryan,
>>>
>>> I have submit a patch for ticket 570.(1) Please provide your feedback
>>> about it. I have a doubt about this patch I want to discuss on IRC. Other
>>> than that I have to discuss some points about the proposal. What time can I
>>> catch you on IRC?
>>>
>>>
>>> https://github.com/dev9226134/bloodhound/commit/0b9c57943a4e98b569eea7185962186153fbea08
>>>
>>>
>>> On Tue, Mar 18, 2014 at 3:44 AM, Ryan Ollos <ry...@wandisco.com>wrote:
>>>
>>>> On Thu, Mar 13, 2014 at 3:01 AM, Devender <de...@gmail.com>wrote:
>>>>
>>>>> Hi Ryan,
>>>>>
>>>>> I have been working on the proposal. I have mentioned some points
>>>>> about the given 6 features. Please provide your feedback on point given
>>>>> below, So that I can come with the concise sub-feature set in these 6
>>>>> features:
>>>>>
>>>>> 1.To add basic feature of a month-long calendar view of a milestone,
>>>>> showing the milestone due date and due date for tickets
>>>>> As given in the ticket #766 (1) we can use the modified trac ticket
>>>>> calender plugin (2), I have installed and tried this plugin.
>>>>> or
>>>>> we can develop the calender view from scratch using basic web
>>>>> development and combine it with the bootstrap to make it look beautiful.
>>>>>
>>>>> Also we can also extend the calender view to google calender as a
>>>>> different plugin in addition to the above plugin (4) but it will be
>>>>> requiring the internet and it is not open source.
>>>>>
>>>>
>>>> Utilizing one of the existing plugins as a starting point seems like
>>>> the best choice. If you need to significantly modify it or rewrite parts of
>>>> the plugin later to fit your needs, then the project can progress in that
>>>> direction.
>>>>
>>>> With regard to Google Calendar, I suppose it would be possible to embed
>>>> a Google Calendar view (or another similar 3rd party calendar into
>>>> Bloodhound). What I would consider doing instead though, is allowing a user
>>>> of Google Calendar to subscribe to the Bloodhound calendar. This would use
>>>> the iCAL or CALDav format. Google Calendar at least supports the iCAL
>>>> format, and you can subscribe to any calendar that is provided in that
>>>> format. I'm not sure if it supports CALDav (and I wasn't even aware of this
>>>> format until Gary mentioned it a few weeks back, so we'd need to
>>>> investigate what use cases it could support).
>>>>
>>>> You might want to consider the "calendar subscription" feature to be
>>>> implemented later in the project, if time allows. It doesn't have to be
>>>> part of the primary deliverable that you are aiming for, but you could
>>>> suggest it as an extra feature that will be added if time allows.
>>>>
>>>>
>>>>> 2. To Allow tickets to be scheduled by drag 'n drop onto the calendar
>>>>> view.
>>>>> First I can make the tickets "div draggable true" and then I can add
>>>>> the basic javascript function (7) i.e what to drag, where to drop and do
>>>>> the drop.
>>>>> or
>>>>> I can use jquery plugin (5).
>>>>>
>>>>
>>>> This sounds good. There are some examples on trac-hacks that you can
>>>> look at to see how the drag and drop functionality might be implemented.
>>>> For example,
>>>> http://trac-hacks.org/wiki/TracDragDropPlugin
>>>> http://trac-hacks.org/wiki/QueuesPlugin
>>>>
>>>>
>>>>> 3. To Scale the view: week, month, year.
>>>>> There is another library mentioned in the ticket #766 as trac week
>>>>> plan plugin (3), I have installed and tried this plugin as well. I can
>>>>> extend this plugin to the month calender as sub plugin and I can create the
>>>>> year plugin similarly as well. So, It will be like calender view containing
>>>>> three view: year, month, and week with month view as default.
>>>>>
>>>>> 4. To add Filters for the calendar view. For example: filter by
>>>>> user, milestone, open/closed tickets.
>>>>> trac calender plugin also contain several filter which are required or
>>>>> If created alone, then also these filters can be done by simple database
>>>>> queries.
>>>>>
>>>>> 5. To Embed the calendar views in the query page and milestone pages.
>>>>> I can put a button in query and milestone page and when user click the
>>>>> button
>>>>> this will add the calender to the right side to the existing page by
>>>>> using jquery. or It will go to the calender page or I can add some
>>>>> indexing based on the jquery tab (6).
>>>>>
>>>>
>>>> I think you have the right idea. Since the milestone view page
>>>> currently displays a table of tickets - the result of a ticket query for
>>>> the milestone - another possibility is to allow the user to toggle between
>>>> the ticket query table and calendar views.
>>>>
>>>>
>>>>> 6. Allow the calendar to be annotated with arbitrary notes/events
>>>>> that do not represent tickets.
>>>>> a new class can be added to the existing trac plugins to support any
>>>>> note feature,
>>>>> these note can be off different color from ticket/milestones.
>>>>>
>>>>
>>>> You seem to have a good grasp of the project. If you want to discuss
>>>> details further, feel free to reply, or else you can catch me on IRC. I'll
>>>> try to be frequently available on IRC over the next several days.
>>>>
>>>
>>> Hi Devender,
>>
>> I copied over the file you'll need to start with in r1578595 and r1578599
>> (1, 2). Now we have bloodhound_theme/bhtheme/templates/bh_product_edit.html
>> which needs to be modified for Bootstrap markup. This consists of basic
>> things like adding the "btn" class to inputs of type "submit", and adding
>> the "row" and "span" classes to divs. To learn the markup, you can compare
>> templates between Trac and Bloodhound. For example, you can diff
>> bloodhound_theme/bhtheme/templates/bh_report_list.html and
>> trac/trac/ticket/templates/report_list.html.
>>
>> The BloodhoundTheme templates are not perfect. Please let us know if you
>> spot any inconsistencies or issues on certain platforms or devices.
>>
>> You can take a look at the recent messages sent to Thimal (3) to get
>> additional pointers. He worked on the template for the Roadmap page, which
>> was committed over the weekend (4). The changes you'll need to make are
>> similar to those made for the Roadmap. Again, it would be good to look at
>> the diffs. You can also view the diffs through the links I sent to Apache
>> ViewVC (which aren't the nicest to view), through your client-side tool or
>> on GitHub (5). For example, the complementary link to (4) on GitHub is (6).
>>
>> (1) http://svn.apache.org/viewvc?view=revision&revision=r1578595
>> (2) http://svn.apache.org/viewvc?view=revision&revision=r1578599
>> (3) http://apache.markmail.org/thread/rnwh5jz3tvxi6kz2
>> (4) http://svn.apache.org/viewvc?view=revision&revision=r1578223
>> (5) https://github.com/apache/bloodhound/commits/trunk
>> (6)
>> https://github.com/apache/bloodhound/commit/5d412c09151c080f826dc595b79e670dc62be7a8
>>
>>
>
Re: GSOC 2014 -- Dynamic calendar and scheduling tools for the
Bloodhound issue tracker
Posted by Devender <de...@gmail.com>.
Hi Ryan,
I have submitted my proposal to GSOC 2014 website(1). Please provide
feedback. I want to submit on the wiki page, please create a page.
(1)
https://www.google-melange.com/gsoc/proposal/public/google/gsoc2014/devenderbindal/5629499534213120
On Thu, Mar 20, 2014 at 8:35 AM, Devender <de...@gmail.com> wrote:
> In previous mail, I forgot to direct to dev@bloodhound.apache.org. So
>
>
> On Thu, Mar 20, 2014 at 8:26 AM, Devender <de...@gmail.com>wrote:
>
>> Hi Ryan,
>>
>> I have submit a patch for ticket 570.(1) Please provide your feedback
>> about it. I have a doubt about this patch I want to discuss on IRC. Other
>> than that I have to discuss some points about the proposal. What time can I
>> catch you on IRC?
>>
>>
>> https://github.com/dev9226134/bloodhound/commit/0b9c57943a4e98b569eea7185962186153fbea08
>>
>>
>> On Tue, Mar 18, 2014 at 3:44 AM, Ryan Ollos <ry...@wandisco.com>wrote:
>>
>>> On Thu, Mar 13, 2014 at 3:01 AM, Devender <de...@gmail.com>wrote:
>>>
>>>> Hi Ryan,
>>>>
>>>> I have been working on the proposal. I have mentioned some points about
>>>> the given 6 features. Please provide your feedback on point given below, So
>>>> that I can come with the concise sub-feature set in these 6 features:
>>>>
>>>> 1.To add basic feature of a month-long calendar view of a milestone,
>>>> showing the milestone due date and due date for tickets
>>>> As given in the ticket #766 (1) we can use the modified trac ticket
>>>> calender plugin (2), I have installed and tried this plugin.
>>>> or
>>>> we can develop the calender view from scratch using basic web
>>>> development and combine it with the bootstrap to make it look beautiful.
>>>>
>>>> Also we can also extend the calender view to google calender as a
>>>> different plugin in addition to the above plugin (4) but it will be
>>>> requiring the internet and it is not open source.
>>>>
>>>
>>> Utilizing one of the existing plugins as a starting point seems like the
>>> best choice. If you need to significantly modify it or rewrite parts of the
>>> plugin later to fit your needs, then the project can progress in that
>>> direction.
>>>
>>> With regard to Google Calendar, I suppose it would be possible to embed
>>> a Google Calendar view (or another similar 3rd party calendar into
>>> Bloodhound). What I would consider doing instead though, is allowing a user
>>> of Google Calendar to subscribe to the Bloodhound calendar. This would use
>>> the iCAL or CALDav format. Google Calendar at least supports the iCAL
>>> format, and you can subscribe to any calendar that is provided in that
>>> format. I'm not sure if it supports CALDav (and I wasn't even aware of this
>>> format until Gary mentioned it a few weeks back, so we'd need to
>>> investigate what use cases it could support).
>>>
>>> You might want to consider the "calendar subscription" feature to be
>>> implemented later in the project, if time allows. It doesn't have to be
>>> part of the primary deliverable that you are aiming for, but you could
>>> suggest it as an extra feature that will be added if time allows.
>>>
>>>
>>>> 2. To Allow tickets to be scheduled by drag 'n drop onto the calendar
>>>> view.
>>>> First I can make the tickets "div draggable true" and then I can add
>>>> the basic javascript function (7) i.e what to drag, where to drop and do
>>>> the drop.
>>>> or
>>>> I can use jquery plugin (5).
>>>>
>>>
>>> This sounds good. There are some examples on trac-hacks that you can
>>> look at to see how the drag and drop functionality might be implemented.
>>> For example,
>>> http://trac-hacks.org/wiki/TracDragDropPlugin
>>> http://trac-hacks.org/wiki/QueuesPlugin
>>>
>>>
>>>> 3. To Scale the view: week, month, year.
>>>> There is another library mentioned in the ticket #766 as trac week plan
>>>> plugin (3), I have installed and tried this plugin as well. I can extend
>>>> this plugin to the month calender as sub plugin and I can create the year
>>>> plugin similarly as well. So, It will be like calender view containing
>>>> three view: year, month, and week with month view as default.
>>>>
>>>> 4. To add Filters for the calendar view. For example: filter by user,
>>>> milestone, open/closed tickets.
>>>> trac calender plugin also contain several filter which are required or
>>>> If created alone, then also these filters can be done by simple database
>>>> queries.
>>>>
>>>> 5. To Embed the calendar views in the query page and milestone pages.
>>>> I can put a button in query and milestone page and when user click the
>>>> button
>>>> this will add the calender to the right side to the existing page by
>>>> using jquery. or It will go to the calender page or I can add some
>>>> indexing based on the jquery tab (6).
>>>>
>>>
>>> I think you have the right idea. Since the milestone view page currently
>>> displays a table of tickets - the result of a ticket query for the
>>> milestone - another possibility is to allow the user to toggle between the
>>> ticket query table and calendar views.
>>>
>>>
>>>> 6. Allow the calendar to be annotated with arbitrary notes/events that
>>>> do not represent tickets.
>>>> a new class can be added to the existing trac plugins to support any
>>>> note feature,
>>>> these note can be off different color from ticket/milestones.
>>>>
>>>
>>> You seem to have a good grasp of the project. If you want to discuss
>>> details further, feel free to reply, or else you can catch me on IRC. I'll
>>> try to be frequently available on IRC over the next several days.
>>>
>>
>> Hi Devender,
>
> I copied over the file you'll need to start with in r1578595 and r1578599
> (1, 2). Now we have bloodhound_theme/bhtheme/templates/bh_product_edit.html
> which needs to be modified for Bootstrap markup. This consists of basic
> things like adding the "btn" class to inputs of type "submit", and adding
> the "row" and "span" classes to divs. To learn the markup, you can compare
> templates between Trac and Bloodhound. For example, you can diff
> bloodhound_theme/bhtheme/templates/bh_report_list.html and
> trac/trac/ticket/templates/report_list.html.
>
> The BloodhoundTheme templates are not perfect. Please let us know if you
> spot any inconsistencies or issues on certain platforms or devices.
>
> You can take a look at the recent messages sent to Thimal (3) to get
> additional pointers. He worked on the template for the Roadmap page, which
> was committed over the weekend (4). The changes you'll need to make are
> similar to those made for the Roadmap. Again, it would be good to look at
> the diffs. You can also view the diffs through the links I sent to Apache
> ViewVC (which aren't the nicest to view), through your client-side tool or
> on GitHub (5). For example, the complementary link to (4) on GitHub is (6).
>
> (1) http://svn.apache.org/viewvc?view=revision&revision=r1578595
> (2) http://svn.apache.org/viewvc?view=revision&revision=r1578599
> (3) http://apache.markmail.org/thread/rnwh5jz3tvxi6kz2
> (4) http://svn.apache.org/viewvc?view=revision&revision=r1578223
> (5) https://github.com/apache/bloodhound/commits/trunk
> (6)
> https://github.com/apache/bloodhound/commit/5d412c09151c080f826dc595b79e670dc62be7a8
>
>
Fwd: GSOC 2014 -- Dynamic calendar and scheduling tools for the
Bloodhound issue tracker
Posted by Devender <de...@gmail.com>.
In previous mail, I forgot to direct to dev@bloodhound.apache.org. So
On Thu, Mar 20, 2014 at 8:26 AM, Devender <de...@gmail.com> wrote:
> Hi Ryan,
>
> I have submit a patch for ticket 570.(1) Please provide your feedback
> about it. I have a doubt about this patch I want to discuss on IRC. Other
> than that I have to discuss some points about the proposal. What time can I
> catch you on IRC?
>
>
> https://github.com/dev9226134/bloodhound/commit/0b9c57943a4e98b569eea7185962186153fbea08
>
>
> On Tue, Mar 18, 2014 at 3:44 AM, Ryan Ollos <ry...@wandisco.com>wrote:
>
>> On Thu, Mar 13, 2014 at 3:01 AM, Devender <de...@gmail.com>wrote:
>>
>>> Hi Ryan,
>>>
>>> I have been working on the proposal. I have mentioned some points about
>>> the given 6 features. Please provide your feedback on point given below, So
>>> that I can come with the concise sub-feature set in these 6 features:
>>>
>>> 1.To add basic feature of a month-long calendar view of a milestone,
>>> showing the milestone due date and due date for tickets
>>> As given in the ticket #766 (1) we can use the modified trac ticket
>>> calender plugin (2), I have installed and tried this plugin.
>>> or
>>> we can develop the calender view from scratch using basic web
>>> development and combine it with the bootstrap to make it look beautiful.
>>>
>>> Also we can also extend the calender view to google calender as a
>>> different plugin in addition to the above plugin (4) but it will be
>>> requiring the internet and it is not open source.
>>>
>>
>> Utilizing one of the existing plugins as a starting point seems like the
>> best choice. If you need to significantly modify it or rewrite parts of the
>> plugin later to fit your needs, then the project can progress in that
>> direction.
>>
>> With regard to Google Calendar, I suppose it would be possible to embed a
>> Google Calendar view (or another similar 3rd party calendar into
>> Bloodhound). What I would consider doing instead though, is allowing a user
>> of Google Calendar to subscribe to the Bloodhound calendar. This would use
>> the iCAL or CALDav format. Google Calendar at least supports the iCAL
>> format, and you can subscribe to any calendar that is provided in that
>> format. I'm not sure if it supports CALDav (and I wasn't even aware of this
>> format until Gary mentioned it a few weeks back, so we'd need to
>> investigate what use cases it could support).
>>
>> You might want to consider the "calendar subscription" feature to be
>> implemented later in the project, if time allows. It doesn't have to be
>> part of the primary deliverable that you are aiming for, but you could
>> suggest it as an extra feature that will be added if time allows.
>>
>>
>>> 2. To Allow tickets to be scheduled by drag 'n drop onto the calendar
>>> view.
>>> First I can make the tickets "div draggable true" and then I can add the
>>> basic javascript function (7) i.e what to drag, where to drop and do the
>>> drop.
>>> or
>>> I can use jquery plugin (5).
>>>
>>
>> This sounds good. There are some examples on trac-hacks that you can look
>> at to see how the drag and drop functionality might be implemented. For
>> example,
>> http://trac-hacks.org/wiki/TracDragDropPlugin
>> http://trac-hacks.org/wiki/QueuesPlugin
>>
>>
>>> 3. To Scale the view: week, month, year.
>>> There is another library mentioned in the ticket #766 as trac week plan
>>> plugin (3), I have installed and tried this plugin as well. I can extend
>>> this plugin to the month calender as sub plugin and I can create the year
>>> plugin similarly as well. So, It will be like calender view containing
>>> three view: year, month, and week with month view as default.
>>>
>>> 4. To add Filters for the calendar view. For example: filter by user,
>>> milestone, open/closed tickets.
>>> trac calender plugin also contain several filter which are required or
>>> If created alone, then also these filters can be done by simple database
>>> queries.
>>>
>>> 5. To Embed the calendar views in the query page and milestone pages.
>>> I can put a button in query and milestone page and when user click the
>>> button
>>> this will add the calender to the right side to the existing page by
>>> using jquery. or It will go to the calender page or I can add some
>>> indexing based on the jquery tab (6).
>>>
>>
>> I think you have the right idea. Since the milestone view page currently
>> displays a table of tickets - the result of a ticket query for the
>> milestone - another possibility is to allow the user to toggle between the
>> ticket query table and calendar views.
>>
>>
>>> 6. Allow the calendar to be annotated with arbitrary notes/events that
>>> do not represent tickets.
>>> a new class can be added to the existing trac plugins to support any
>>> note feature,
>>> these note can be off different color from ticket/milestones.
>>>
>>
>> You seem to have a good grasp of the project. If you want to discuss
>> details further, feel free to reply, or else you can catch me on IRC. I'll
>> try to be frequently available on IRC over the next several days.
>>
>
> Hi Devender,
I copied over the file you'll need to start with in r1578595 and r1578599
(1, 2). Now we have bloodhound_theme/bhtheme/templates/bh_product_edit.html
which needs to be modified for Bootstrap markup. This consists of basic
things like adding the "btn" class to inputs of type "submit", and adding
the "row" and "span" classes to divs. To learn the markup, you can compare
templates between Trac and Bloodhound. For example, you can diff
bloodhound_theme/bhtheme/templates/bh_report_list.html and
trac/trac/ticket/templates/report_list.html.
The BloodhoundTheme templates are not perfect. Please let us know if you
spot any inconsistencies or issues on certain platforms or devices.
You can take a look at the recent messages sent to Thimal (3) to get
additional pointers. He worked on the template for the Roadmap page, which
was committed over the weekend (4). The changes you'll need to make are
similar to those made for the Roadmap. Again, it would be good to look at
the diffs. You can also view the diffs through the links I sent to Apache
ViewVC (which aren't the nicest to view), through your client-side tool or
on GitHub (5). For example, the complementary link to (4) on GitHub is (6).
(1) http://svn.apache.org/viewvc?view=revision&revision=r1578595
(2) http://svn.apache.org/viewvc?view=revision&revision=r1578599
(3) http://apache.markmail.org/thread/rnwh5jz3tvxi6kz2
(4) http://svn.apache.org/viewvc?view=revision&revision=r1578223
(5) https://github.com/apache/bloodhound/commits/trunk
(6)
https://github.com/apache/bloodhound/commit/5d412c09151c080f826dc595b79e670dc62be7a8
Re: GSOC 2014 -- Dynamic calendar and scheduling tools for the
Bloodhound issue tracker
Posted by Devender <de...@gmail.com>.
Hi Ryan,
I have been working on the proposal. I have mentioned some points about the
given 6 features. Please provide your feedback on point given below, So
that I can come with the concise sub-feature set in these 6 features:
1.To add basic feature of a month-long calendar view of a milestone,
showing the milestone due date and due date for tickets
As given in the ticket #766 (1) we can use the modified trac ticket
calender plugin (2), I have installed and tried this plugin.
or
we can develop the calender view from scratch using basic web development
and combine it with the bootstrap to make it look beautiful.
Also we can also extend the calender view to google calender as a different
plugin in addition to the above plugin (4) but it will be requiring the
internet and it is not open source.
2. To Allow tickets to be scheduled by drag 'n drop onto the calendar view.
First I can make the tickets "div draggable true" and then I can add the
basic javascript function (7) i.e what to drag, where to drop and do the
drop.
or
I can use jquery plugin (5).
3. To Scale the view: week, month, year.
There is another library mentioned in the ticket #766 as trac week plan
plugin (3), I have installed and tried this plugin as well. I can extend
this plugin to the month calender as sub plugin and I can create the year
plugin similarly as well. So, It will be like calender view containing
three view: year, month, and week with month view as default.
4. To add Filters for the calendar view. For example: filter by user,
milestone, open/closed tickets.
trac calender plugin also contain several filter which are required or If
created alone, then also these filters can be done by simple database
queries.
5. To Embed the calendar views in the query page and milestone pages.
I can put a button in query and milestone page and when user click the
button
this will add the calender to the right side to the existing page by using
jquery. or It will go to the calender page or I can add some indexing based
on the jquery tab (6).
6. Allow the calendar to be annotated with arbitrary notes/events that do
not represent tickets.
a new class can be added to the existing trac plugins to support any note
feature,
these note can be off different color from ticket/milestones.
In my last email, I have attached the basic product edit template but that
file missing a link, so I am attaching it again. Other than that I am
working on the ticket #570.
(1) https://issues.apache.org/bloodhound/ticket/766
(2) https://trac-hacks.org/wiki/TicketCalendarPlugin
(3) https://trac-hacks.org/wiki/WeekPlanPlugin
(4) https://en.wikipedia.org/wiki/Google_Calendar
(5) http://jqueryui.com/draggable/
(6) http://jqueryui.com/tabs/
(7) http://www.w3schools.com/html/html5_draganddrop.asp
On Tue, Mar 11, 2014 at 6:18 PM, Devender <de...@gmail.com> wrote:
> Hi Ryan,
>
> I have studied about the bootstrap 2.3 documentation and I have worked
> with some samples of the bootstrap. I am attaching the modified version of
> the signup (1) example of the bootstrap that can work for the basic product
> edit for the desktop. I have also read about the genshi (2) and I have done
> the above 3 points mentioned in last mail but I want some pointers to start
> merge this code to create the template for product edit and become
> familiarize with the bloodhound code.
>
> (1) http://getbootstrap.com/examples/signin/
> (2) http://genshi.edgewall.org/wiki/Documentation/xml-templates.html
>
>
> On Mon, Mar 10, 2014 at 9:00 PM, Ryan Ollos <ry...@wandisco.com>wrote:
>
>> On Mon, Mar 10, 2014 at 2:23 AM, Ryan Ollos <ry...@wandisco.com>wrote:
>>
>>> On Mon, Mar 10, 2014 at 2:02 AM, Devender <de...@gmail.com>wrote:
>>>
>>>> Hi Ryan,
>>>>
>>>> I am a 4th year student of the Department of Computer Science and
>>>> Engineering at Indian Institute of Technology( IIT), Kharagpur, India.
>>>>
>>>> I am good at programming in Python, AJAX, PHP, MySQL, JavaScript,
>>>> jQuery, HTML, CSS and C++. I have worked on projects which used python
>>>> and web development technologies.
>>>>
>>>> I am very enthusiast to work with Apache in GSOC 2014. I have
>>>> installed and used the bloodhound and I am interested to work on this idea (
>>>> COMDEV-112 <https://issues.apache.org/jira/browse/COMDEV-112>). I have
>>>> done setup for the basic development environment for Bloodhound. I
>>>> have been looking at the starter ticket<https://issues.apache.org/bloodhound/query?status=!closed&keywords=~starter>
>>>> *,* but I don't know which ticket I should work on. Please guide me to
>>>> proceed for my proposal.
>>>>
>>>
>>> Hi Devender,
>>>
>>> Welcome!
>>>
>>> It might be good to familiarize yourself with Bootstrap by working
>>> ticket #570 (1). To get started,
>>> 1. Review the Bootstrap 2.3 documents
>>> 2. Copy the template
>>> bloodhound_multiproduct/multiproduct/templates/product_edit.html to
>>> bloodhound_theme/bhtheme/templates/bh_product_edit.html
>>> 3. Add bh_product_edit.html to the template map in
>>> bloodhound_theme/bhtheme/theme.py
>>> 4. Modify the markup in the template so that we get nice styling on
>>> multiple devices (desktop, tablet, mobile).
>>>
>>> You can study the other templates in bloodhound_theme to learn how the
>>> Boostrap markup can be used.
>>>
>>> For the COMDEV-112 project, it is a bit open-ended, which gives you a
>>> lot of room to work with the community to define the solution. You can get
>>> started by looking at the architecture of the plugins mentioned in #766 (3).
>>>
>>> (1) https://issues.apache.org/bloodhound/ticket/570
>>> (2) http://getbootstrap.com/2.3.2/
>>> (3) https://issues.apache.org/bloodhound/ticket/766
>>>
>>>
>> Devender, I didn't notice initially that you sent the email directly to
>> me. This is just a quick note to say that future emails should be directed
>> to the dev@bloodhound.apache.org list, which I've added to the Reply of
>> this email. This is to keep the whole Bloodhound community involved in your
>> project :)
>>
>
>
Re: GSOC 2014 -- Dynamic calendar and scheduling tools for the
Bloodhound issue tracker
Posted by Devender <de...@gmail.com>.
Hi Ryan,
I have studied about the bootstrap 2.3 documentation and I have worked with
some samples of the bootstrap. I am attaching the modified version of the
signup (1) example of the bootstrap that can work for the basic product
edit for the desktop. I have also read about the genshi (2) and I have done
the above 3 points mentioned in last mail but I want some pointers to start
merge this code to create the template for product edit and become
familiarize with the bloodhound code.
(1) http://getbootstrap.com/examples/signin/
(2) http://genshi.edgewall.org/wiki/Documentation/xml-templates.html
On Mon, Mar 10, 2014 at 9:00 PM, Ryan Ollos <ry...@wandisco.com> wrote:
> On Mon, Mar 10, 2014 at 2:23 AM, Ryan Ollos <ry...@wandisco.com>wrote:
>
>> On Mon, Mar 10, 2014 at 2:02 AM, Devender <de...@gmail.com>wrote:
>>
>>> Hi Ryan,
>>>
>>> I am a 4th year student of the Department of Computer Science and
>>> Engineering at Indian Institute of Technology( IIT), Kharagpur, India.
>>>
>>> I am good at programming in Python, AJAX, PHP, MySQL, JavaScript,
>>> jQuery, HTML, CSS and C++. I have worked on projects which used python
>>> and web development technologies.
>>>
>>> I am very enthusiast to work with Apache in GSOC 2014. I have installed
>>> and used the bloodhound and I am interested to work on this idea (
>>> COMDEV-112 <https://issues.apache.org/jira/browse/COMDEV-112>). I have
>>> done setup for the basic development environment for Bloodhound. I have
>>> been looking at the starter ticket<https://issues.apache.org/bloodhound/query?status=!closed&keywords=~starter>
>>> *,* but I don't know which ticket I should work on. Please guide me to
>>> proceed for my proposal.
>>>
>>
>> Hi Devender,
>>
>> Welcome!
>>
>> It might be good to familiarize yourself with Bootstrap by working ticket
>> #570 (1). To get started,
>> 1. Review the Bootstrap 2.3 documents
>> 2. Copy the template
>> bloodhound_multiproduct/multiproduct/templates/product_edit.html to
>> bloodhound_theme/bhtheme/templates/bh_product_edit.html
>> 3. Add bh_product_edit.html to the template map in
>> bloodhound_theme/bhtheme/theme.py
>> 4. Modify the markup in the template so that we get nice styling on
>> multiple devices (desktop, tablet, mobile).
>>
>> You can study the other templates in bloodhound_theme to learn how the
>> Boostrap markup can be used.
>>
>> For the COMDEV-112 project, it is a bit open-ended, which gives you a lot
>> of room to work with the community to define the solution. You can get
>> started by looking at the architecture of the plugins mentioned in #766 (3).
>>
>> (1) https://issues.apache.org/bloodhound/ticket/570
>> (2) http://getbootstrap.com/2.3.2/
>> (3) https://issues.apache.org/bloodhound/ticket/766
>>
>>
> Devender, I didn't notice initially that you sent the email directly to
> me. This is just a quick note to say that future emails should be directed
> to the dev@bloodhound.apache.org list, which I've added to the Reply of
> this email. This is to keep the whole Bloodhound community involved in your
> project :)
>