Comments (13)
mridulnagpal
commented on July 29, 2024
Sure, I can try it!!
from leaflet-blurred-location.
mridulnagpal
commented on July 29, 2024
What do you suggest a feature or a library by itself?
from leaflet-blurred-location.
jywarren
commented on July 29, 2024
Well, what do you think of my proposed method above? Can you initialize BlurredLocation() without providing the HTML inputs, and will it cause errors? I guess perhaps this is a different function and could be provided via a separate library to keep things really distinct. Which makes more sense to you?
from leaflet-blurred-location.
mridulnagpal
commented on July 29, 2024
For BlurredLocation() I need a number of html DOM elements I have set up inside of it, so yes it will give errors. Easier way would be adding it as a feature, but if you can think of any other I will be happy to learn!!
from leaflet-blurred-location.
mridulnagpal
commented on July 29, 2024
@jywarren So I looked into ways of making this work without html but couldn't. Should I make it as a new feature or do we need to stick to a different library only?
from leaflet-blurred-location.
jywarren
commented on July 29, 2024
What do you think of moving the constructor itself into a submethod like
BlurredLocation.Input() vs BlurredLocation.Layer()?
…On Aug 16, 2017 12:34 AM, "Mridul Nagpal" ***@***.***> wrote:
@jywarren <https://github.com/jywarren> So I looked into ways of making
this work without html but couldn't. Should I make it as a new feature or
do we need to stick to a different library only?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#84 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABfJ7FezHObNXAmUl1wG8zJdraiGPPZks5sYg7RgaJpZM4O1g5K>
.
from leaflet-blurred-location.
jywarren
commented on July 29, 2024
Or if there really is no shared code between the input library (that you've
completed) and the new display library, let's make a separate lib called
BlurredLocationDisplay, what do you think?
…On Aug 16, 2017 4:51 PM, "Jeffrey Warren" ***@***.***> wrote:
What do you think of moving the constructor itself into a submethod like
BlurredLocation.Input() vs BlurredLocation.Layer()?
On Aug 16, 2017 12:34 AM, "Mridul Nagpal" ***@***.***>
wrote:
> @jywarren <https://github.com/jywarren> So I looked into ways of making
> this work without html but couldn't. Should I make it as a new feature or
> do we need to stick to a different library only?
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#84 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AABfJ7FezHObNXAmUl1wG8zJdraiGPPZks5sYg7RgaJpZM4O1g5K>
> .
>
from leaflet-blurred-location.
mridulnagpal
commented on July 29, 2024
I think we might be able to make it into a new library and integrate it to publiclab separately. Can you create a new repo for the same? For the new lib?
from leaflet-blurred-location.
mridulnagpal
commented on July 29, 2024
@jywarren What all things do you want me to do before the deadline, as I
recieved a mail from google regarding submission
…On 16-Aug-2017 7:24 PM, "Jeffrey Warren" ***@***.***> wrote:
Or if there really is no shared code between the input library (that you've
completed) and the new display library, let's make a separate lib called
BlurredLocationDisplay, what do you think?
On Aug 16, 2017 4:51 PM, "Jeffrey Warren" ***@***.***> wrote:
> What do you think of moving the constructor itself into a submethod like
> BlurredLocation.Input() vs BlurredLocation.Layer()?
>
> On Aug 16, 2017 12:34 AM, "Mridul Nagpal" ***@***.***>
> wrote:
>
>> @jywarren <https://github.com/jywarren> So I looked into ways of making
>> this work without html but couldn't. Should I make it as a new feature
or
>> do we need to stick to a different library only?
>>
>> —
>> You are receiving this because you were mentioned.
>> Reply to this email directly, view it on GitHub
>> <https://github.com/publiclab/leaflet-blurred-location/
issues/84#issuecomment-322596258>,
>> or mute the thread
>> <https://github.com/notifications/unsubscribe-auth/
AABfJ7FezHObNXAmUl1wG8zJdraiGPPZks5sYg7RgaJpZM4O1g5K>
>> .
>>
>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#84 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AVULlDazlo9KlXJqzKVLMZpKLFuiiscGks5sYvSkgaJpZM4O1g5K>
.
from leaflet-blurred-location.
mridulnagpal
commented on July 29, 2024
@jywarren Haven't heard from you in a while so creating a repo on my own
and setting it up. Please reply ASAP
On 18-Aug-2017 2:28 PM, "Mridul Nagpal" <[email protected]> wrote:
@jywarren What all things do you want me to do before the deadline, as I
recieved a mail from google regarding submission
…On 16-Aug-2017 7:24 PM, "Jeffrey Warren" ***@***.***> wrote:
Or if there really is no shared code between the input library (that you've
completed) and the new display library, let's make a separate lib called
BlurredLocationDisplay, what do you think?
On Aug 16, 2017 4:51 PM, "Jeffrey Warren" ***@***.***> wrote:
> What do you think of moving the constructor itself into a submethod like
> BlurredLocation.Input() vs BlurredLocation.Layer()?
>
> On Aug 16, 2017 12:34 AM, "Mridul Nagpal" ***@***.***>
> wrote:
>
>> @jywarren <https://github.com/jywarren> So I looked into ways of making
>> this work without html but couldn't. Should I make it as a new feature
or
>> do we need to stick to a different library only?
>>
>> —
>> You are receiving this because you were mentioned.
>> Reply to this email directly, view it on GitHub
>> <https://github.com/publiclab/leaflet-blurred-location/issue
s/84#issuecomment-322596258>,
>> or mute the thread
>> <https://github.com/notifications/unsubscribe-auth/AABfJ7Fez
HObNXAmUl1wG8zJdraiGPPZks5sYg7RgaJpZM4O1g5K>
>> .
>>
>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#84 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AVULlDazlo9KlXJqzKVLMZpKLFuiiscGks5sYvSkgaJpZM4O1g5K>
.
from leaflet-blurred-location.
jywarren
commented on July 29, 2024
Please do, and call it Leaflet.BlurredLocationDisplay for now!
…On Aug 20, 2017 10:48 AM, "Mridul Nagpal" ***@***.***> wrote:
@jywarren Haven't heard from you in a while so creating a repo on my own
and setting it up. Please reply ASAP
On 18-Aug-2017 2:28 PM, "Mridul Nagpal" ***@***.***> wrote:
@jywarren What all things do you want me to do before the deadline, as I
recieved a mail from google regarding submission
On 16-Aug-2017 7:24 PM, "Jeffrey Warren" ***@***.***> wrote:
> Or if there really is no shared code between the input library (that
you've
> completed) and the new display library, let's make a separate lib called
> BlurredLocationDisplay, what do you think?
>
> On Aug 16, 2017 4:51 PM, "Jeffrey Warren" ***@***.***> wrote:
>
> > What do you think of moving the constructor itself into a submethod
like
> > BlurredLocation.Input() vs BlurredLocation.Layer()?
> >
> > On Aug 16, 2017 12:34 AM, "Mridul Nagpal" ***@***.***>
> > wrote:
> >
> >> @jywarren <https://github.com/jywarren> So I looked into ways of
making
> >> this work without html but couldn't. Should I make it as a new feature
> or
> >> do we need to stick to a different library only?
> >>
> >> —
> >> You are receiving this because you were mentioned.
> >> Reply to this email directly, view it on GitHub
> >> <https://github.com/publiclab/leaflet-blurred-location/issue
> s/84#issuecomment-322596258>,
> >> or mute the thread
> >> <https://github.com/notifications/unsubscribe-auth/AABfJ7Fez
> HObNXAmUl1wG8zJdraiGPPZks5sYg7RgaJpZM4O1g5K>
> >> .
> >>
> >
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <https://github.com/publiclab/leaflet-blurred-location/
issues/84#issuecomment-322778527>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/
AVULlDazlo9KlXJqzKVLMZpKLFuiiscGks5sYvSkgaJpZM4O1g5K>
> .
>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#84 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABfJ64XZgOCF7TJ0JJpGb6RGSIsCzySks5sZ-TmgaJpZM4O1g5K>
.
from leaflet-blurred-location.
jywarren
commented on July 29, 2024
On Aug 20, 2017 10:50 AM, "Jeffrey Warren" ***@***.***> wrote:
Please do, and call it Leaflet.BlurredLocationDisplay for now!
On Aug 20, 2017 10:48 AM, "Mridul Nagpal" ***@***.***>
wrote:
> @jywarren Haven't heard from you in a while so creating a repo on my own
> and setting it up. Please reply ASAP
>
>
> On 18-Aug-2017 2:28 PM, "Mridul Nagpal" ***@***.***> wrote:
>
> @jywarren What all things do you want me to do before the deadline, as I
> recieved a mail from google regarding submission
>
> On 16-Aug-2017 7:24 PM, "Jeffrey Warren" ***@***.***>
> wrote:
>
> > Or if there really is no shared code between the input library (that
> you've
> > completed) and the new display library, let's make a separate lib called
> > BlurredLocationDisplay, what do you think?
> >
> > On Aug 16, 2017 4:51 PM, "Jeffrey Warren" ***@***.***> wrote:
> >
> > > What do you think of moving the constructor itself into a submethod
> like
> > > BlurredLocation.Input() vs BlurredLocation.Layer()?
> > >
> > > On Aug 16, 2017 12:34 AM, "Mridul Nagpal" ***@***.***>
> > > wrote:
> > >
> > >> @jywarren <https://github.com/jywarren> So I looked into ways of
> making
> > >> this work without html but couldn't. Should I make it as a new
> feature
> > or
> > >> do we need to stick to a different library only?
> > >>
> > >> —
> > >> You are receiving this because you were mentioned.
> > >> Reply to this email directly, view it on GitHub
> > >> <https://github.com/publiclab/leaflet-blurred-location/issue
> > s/84#issuecomment-322596258>,
> > >> or mute the thread
> > >> <https://github.com/notifications/unsubscribe-auth/AABfJ7Fez
> > HObNXAmUl1wG8zJdraiGPPZks5sYg7RgaJpZM4O1g5K>
> > >> .
> > >>
> > >
> >
> > —
> > You are receiving this because you commented.
> > Reply to this email directly, view it on GitHub
> > <https://github.com/publiclab/leaflet-blurred-location/issue
> s/84#issuecomment-322778527>,
> > or mute the thread
> > <https://github.com/notifications/unsubscribe-auth/AVULlDazl
> o9KlXJqzKVLMZpKLFuiiscGks5sYvSkgaJpZM4O1g5K>
> > .
> >
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#84 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AABfJ64XZgOCF7TJ0JJpGb6RGSIsCzySks5sZ-TmgaJpZM4O1g5K>
> .
>
from leaflet-blurred-location.
mridulnagpal
commented on July 29, 2024
Thanks ! :)
…On 20-Aug-2017 1:23 PM, "Jeffrey Warren" ***@***.***> wrote:
Ok I did it!
https://github.com/publiclab/Leaflet.BlurredLocationDisplay
On Aug 20, 2017 10:50 AM, "Jeffrey Warren" ***@***.***> wrote:
> Please do, and call it Leaflet.BlurredLocationDisplay for now!
>
> On Aug 20, 2017 10:48 AM, "Mridul Nagpal" ***@***.***>
> wrote:
>
>> @jywarren Haven't heard from you in a while so creating a repo on my own
>> and setting it up. Please reply ASAP
>>
>>
>> On 18-Aug-2017 2:28 PM, "Mridul Nagpal" ***@***.***>
wrote:
>>
>> @jywarren What all things do you want me to do before the deadline, as I
>> recieved a mail from google regarding submission
>>
>> On 16-Aug-2017 7:24 PM, "Jeffrey Warren" ***@***.***>
>> wrote:
>>
>> > Or if there really is no shared code between the input library (that
>> you've
>> > completed) and the new display library, let's make a separate lib
called
>> > BlurredLocationDisplay, what do you think?
>> >
>> > On Aug 16, 2017 4:51 PM, "Jeffrey Warren" ***@***.***> wrote:
>> >
>> > > What do you think of moving the constructor itself into a submethod
>> like
>> > > BlurredLocation.Input() vs BlurredLocation.Layer()?
>> > >
>> > > On Aug 16, 2017 12:34 AM, "Mridul Nagpal" ***@***.***
>
>> > > wrote:
>> > >
>> > >> @jywarren <https://github.com/jywarren> So I looked into ways of
>> making
>> > >> this work without html but couldn't. Should I make it as a new
>> feature
>> > or
>> > >> do we need to stick to a different library only?
>> > >>
>> > >> —
>> > >> You are receiving this because you were mentioned.
>> > >> Reply to this email directly, view it on GitHub
>> > >> <https://github.com/publiclab/leaflet-blurred-location/issue
>> > s/84#issuecomment-322596258>,
>> > >> or mute the thread
>> > >> <https://github.com/notifications/unsubscribe-auth/AABfJ7Fez
>> > HObNXAmUl1wG8zJdraiGPPZks5sYg7RgaJpZM4O1g5K>
>> > >> .
>> > >>
>> > >
>> >
>> > —
>> > You are receiving this because you commented.
>> > Reply to this email directly, view it on GitHub
>> > <https://github.com/publiclab/leaflet-blurred-location/issue
>> s/84#issuecomment-322778527>,
>> > or mute the thread
>> > <https://github.com/notifications/unsubscribe-auth/AVULlDazl
>> o9KlXJqzKVLMZpKLFuiiscGks5sYvSkgaJpZM4O1g5K>
>> > .
>> >
>>
>> —
>> You are receiving this because you were mentioned.
>> Reply to this email directly, view it on GitHub
>> <https://github.com/publiclab/leaflet-blurred-location/
issues/84#issuecomment-323569712>,
>> or mute the thread
>> <https://github.com/notifications/unsubscribe-auth/
AABfJ64XZgOCF7TJ0JJpGb6RGSIsCzySks5sZ-TmgaJpZM4O1g5K>
>> .
>>
>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#84 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AVULlAFqz0RK4nmaLQw7Jt8VcxMTcTmhks5sZ-X-gaJpZM4O1g5K>
.
from leaflet-blurred-location.
Related Issues (20)
- Restrict out of range input HOT 1
- Make LBL object syntax same as that of standard leaflet object .
- [Bug] TypeError: getBlurryScale(...) is undefined .
- Weekly Community Check-in #19 - Express gratitude :-) HOT 43
- Development of a "blurred location" specification/standard
- Add CONTRIBUTING.md HOT 8
- Remove Bower support HOT 6
- Grid box selection not working between 1W and 0 degrees longitude
- Location search not working HOT 33
- Open a ISSUE TEMPLATE [ First Timers Only ] HOT 8
- Create getZoom function HOT 1
- Create getZoomFromCoordinates function HOT 18
- Add new functions to README HOT 3
- Weekly community Check-In #42 - Happy Holidays HOT 18
- Slider doesn't update when map is zoomed with other methods
- Geocode reverse lookup in getPlacenameFromCoordinates not working HOT 1
- Testing errors - ReferenceError: Can't find variable: google HOT 9
- Weekly community Check-In #50 - Favorite text editors HOT 16
- Mapknitter API change
- Demo problem
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from leaflet-blurred-location.